...

Test cases  from upstream projects will be validated and work in conjunction with each other as an organic whole. To achieve this goal,  we need bunch of scripts to communicate with these test cases. The scripts can execute the test cases under certain circumstances, and then analysis variety results to make a human-friendly report . 

• config: basiclly the same env config files as the config files in functest/yardstick, used to indicate SUT information
• testcases: testcase definition files, mapping to the testcase from functest/yardstick being executed. these testcases comprise the certification
• certification: certification definition files, to determine the scenario of the SUT, and a collection of testcases.
• parser: parse, load and check input files(config,certification,testcases) whether they are valid.
• downloader: get functest/yardstick repos if they are not existed.
• runner: execute testcases from functest/yardstick.
• report: generate reports from test results.
• dashboard: presentation of test report and show the details of each testcase.

.

Testcase report analysis

As our certification reports come from the report of test cases, we have to check those test cases one by one. And the most important data is the test case details. Test case details include its duration, test case names , etc. So i make a table to show the differences between test cases.

...