...
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 .
Component | Description | Status | ||
config | basiclly the same env config as the config in functest/yardstick, used to indicate SUT information | OngoingDone | ||
Testcase file | testcase definition files, mapping to the testcase from functest/yardstick being executed. these testcases comprise the certification | Ongoing one by one | Done | |
testsuite | testsuite | certification | certification definition files, to determine the scenario of the SUT, and a collection of testcases | Done, basic definition |
parser | parse, load and check input files(config,certification,testcases) if they are valid | Done, basic function | ||
Testcase keeper | Testcase management, execution status , etcOngoing, | Done | ||
| Test Runner | different runner for different test case type. | Done | ||
Container manager | all stuff around the container, like pull image, start container and exec cmd in container | Ongoing, need support yardstickDone | ||
runner | main entry for running through the whole validating procedure | OngoingDone | ||
report | manage test results and generate reports from these results | Ongoing, just begin to work on itDone | ||
dashboard | presentation of test report and show the details of each testcase | Optional |
...