This page provides information about the Dovetail Test Tool. The Dovetail Test Tool is designed to leverage existing OPNFV test projects (such as functest and yardstick) to automate the execution of Dovetail Test Cases in a way that satisfies compliance testing requirements, and generate required reports for use by the OPNFV compliance verification program.
Dovetail Test Tool Design
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 | Ongoing |
Testcase file | testcase definition files, mapping to the testcase from functest/yardstick being executed. these testcases comprise the certification | Ongoing one by one |
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 , etc | Ongoing, |
Container manager | all stuff around the container, like pull image, start container and exec cmd in container | Ongoing, need support yardstick |
runner | main entry for running through the whole validating procedure | Ongoing |
report | manage test results and generate reports from these results | Ongoing, just begin to work on it |
dashboard | presentation of test report and show the details of each testcase | Optional |
.
Dovetail Test Definition Files
Dovetail uses two levels of definition files to specify what exact test cases are to be executed in a given test run or test suite specification.
Test Suite Definition File
This file defines a suite that is comprised of test cases which may be a partial list of all existing test cases. It gives the suite a name that is more convenient for reference.
- certification_basic: test suite name
- testcase_list: a list of test case referenced to be in the named test suite
Test Case Definition File
- dovetail.feature.tc003: name of the test case, comprised of 3 parts, the dovetail project, belongs to which feature, and the serial number
- objective: a brief description of the test case, explains the objective of this test case
- scripts: scripts and configurations for the execution of the test case
- type: upstream testing project
- testcase: the input parameter for the execution of the upstream testing scripts
- sub_testcase_list: a list of real working test, indicated what's inside of this test case
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.