Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Test_API Enhancement (in Details section)

Id :
Build tag :
Case name :
Criteria :
Installer :
Pod name :
Project name :
Scenario :
Start date :
Stop date :
Version :
Details :
{
standards_ref: (cntt requirement, etsi tst, nomenclature)
performance: true/false
threshold: (for pass/fail criteria)
metric: (us, bps, ....)
links to OPNFV Artifact: (configuration file, env-details, csvs, )
....
}

Further Discussion on Test API Test DB at the April 2020 Virtual Event

What project will own and maintain the code for this? Releng(no opinion, just the home for the code) - Dovetail - X-testing (a project that lives under Functest)

  • Releng - testresults project volunteers - none so far?  Trevor Bramwell's e-mail

Who consumes the Details field info, such as the test case requirement names/nomenclature from CNTT RA CH3 ??

  • Test fails - Are the Requirements that were tested MUST or SHOULD? Some SHOULDs will be allowed exceptions, is this one of them? SHOULDs are intended to be conditional MUSTs.
  • Conclusion: Dovetail web portal and the badging process are the consumers.

Other Topics/Options:

  • Current Test API Case name: a string that we augment with the CNTT RX Ch3 Requirement?
  • Issue: a Pod name: must exist in the POD Table of Test API for a test to report a test result.
  • Issue: Scenarios need to be populated, and exist in an Scenario Table.
  • Question: can a version 2.0 of the test API be defined?  (with the enhancements as simple Key - Value pairs (not Details), and AVOID breaking all current inputs.
  • Mark displayed the Web interface to the Test Results. Some Projects are not updating tests.

Summary: further details on approach discussed, but there is no success without an active project or team to take-up the needed development and help OPNFV projects to evolve to the enhanced/2.0 version!


Test_API Enhancement (in Details section)

Id :
Build tag :
Case name :
Criteria :
Installer :
Pod name :
Project name :
Scenario :
Start date :
Stop date :
Version :
Details :
{
standards_ref: (cntt requirement, etsi tst, nomenclature)
performance: true/false
threshold: (for pass/fail criteria)
metric: (us, bps, ....)
links to OPNFV Artifact: (configuration file, env-details, csv files, )
....
}