Dovetail Test Case Detailed Reports
Test case detail reports come from existing test projects that implemented the respective tests. A given report may or may not be suitable or sufficient for CVP purposes. This section is WORK IN PROGRESS.
Below are some known information about the status of these reports, as we make preliminary analysis of FuncTest and Yardstick test cases.
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 details of testcases.
- duration: whether result has a duration of executing time
- sub-testcase: whether result contains any sub-testcase
- details on success: whether result contains details of sub-testcase, like testcase name, parent testcase, etc, when pass
- details on fail: whether result contains details of sub-testcase when fail
FuncTest Test Report Status
Test-case | duration | sub-testcase | details on pass | details on fail |
healthcheck | ||||
tempest_smoke_serial | Y | Y | N | Y |
vping_ssh | Y | N | N | N |
vping_userdata | Y | N | N | N |
rally_sanity | Y | Y | N | N |
Tempest_full_parallel | ||||
| rally_full |
Yardstick Test Report Status
Well, yardstick is much simpler than functest, it has same result format for each test case.
The most important part of yardstick test result is the metrics of every sequence which we do not need it at all.
We just need to know that the test case pass or fail.
Dovetail Test Run Summary Report
The Dovetail Test Run Summary Report is to aid the determination of test result for CVP.
Shown below is a sample output of current version of implementation. It is WORK IN PROGRESS.
