summaryrefslogtreecommitdiffstats
path: root/etc/compliance/proposed_tests.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-07-25Cleaning up proposed-tests test suiteGeorg Kunz1-26/+1
We have moved all newly proposed tests to the next OVP test suite, so these tests do not need to be in here anymore - and do not need to be run in CI. Change-Id: I5f51b76a37b706c5b4abc75272ad799a72841f67 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-07-24Making the results file a proper json fileGeorg Kunz1-1/+1
The results.json file is currently not a properly formated json file, but contains one json structure per line/testcase. Whit this change, all test results are being collected at runtime and then written to a properly formated json file at the end of a test run. Moreover, this patch introduces 'mandatory' and 'optional' sections to the test suites definition files in order to clearly indicate if a test is part of the corresponding test scope. The web portal needs to be adapted accordingly to be able to read the new results file. JIRA: DOVETAIL-672 Change-Id: Id0706c7e82622fc9c2c2fece26b2d6c07c1580be Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-07-17Update test suite ovp.nextxudan1-25/+27
Update test suite ovp.next according to the latest OVP scope. Modify Dovetail daily jobs to run all the scope. There should be 2 jobs. One for all mandatory test cases and the other for all optional ones. That's mainly because of that the total executed time will be too large (more than 300 minutes). Then the job will always failed because of time out. It's hard to enlarge the time because it's already larger than common 3 hours. Split it into 2 jobs can avoid the time out issue and make the results clearer for reviewing. JIRA: DOVETAIL-694 Change-Id: Ie0ea6221868941781af1477f7c7719f7cb4351a4 Signed-off-by: xudan <xudan16@huawei.com>
2018-07-02Splitting the networking tests in API and scenario testsGeorg Kunz1-1/+2
Split the networking tempest test case in Tempest API tests and scenario tests. The API tests will be promoted to mandatory while the scenario tests will remain optional. JIRA: DOVETAIL-678 Change-Id: I03022316076809536782e82fd531d98f45105caa Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-29Adding vEPC test case to Dovetail and proposed_tests suiteGeorg Kunz1-0/+1
Adding the vEPC test case to Dovetail. The test deploys a vEPC using Juju as VNF manager and performs application level tests. JIRA: DOVETAIL-650 Change-Id: I15c2cdddee510e12a5faf18efc8950af5cf7b664 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-18Got an exception when test suite is emptyxudan1-8/+8
1. Return empty test case list when test suite is empty. 2. Don't quite understand why comment out all proposed_tests. 3. Move stress ping test case at the end of the list, because it may broken the message queue. Change-Id: Ib717fc91e3763be03f243f82e53679462ecdae04 Signed-off-by: xudan <xudan16@huawei.com>
2018-05-17Adding OpenStack controller database HA test caseGeorg Kunz1-15/+16
Adding the OpenStack controller database HA test case (Yardstick tc090) to Dovetail and the proposed_tests test suite. JIRA: DOVETAIL-654 Change-Id: I4d20b907de8df2e9567891354b49e832cce13c7c Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-15Renaming test cases for better readabilityGeorg Kunz1-17/+15
This patchset proposes a new naming scheme for test cases. The ides is to replace the current numbered scheme <testarea>.tc<number> with: <testarea>.<capability/test case description> The motivation for this is that a the numbering does not convey any information about what the test case is doing and hides to which test case implementation in Functest or Yardstick a test case spec refers. Note: this patchset has not yet been tested in Dovetail itself. Its goal is start a discussion about the naming scheme. JIRA: DOVETAIL-647 Change-Id: If33b4bf88e451b372c2af10895ff92a87d9d961d Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-15Split tempest_smoke test casexudan1-1/+8
1. Total number of sub test cases is 119 2. Remove all 14 object_storage test cases which need swift 3. Remove 26 test cases already included in osinterop test area 4. Remove 21 test cases already included in ipv6 test area 5. Remove 2 scenario test cases already included in tempest test area 6. Split other 56 test cases into 8 groups Change-Id: I9eef20593ebf5f69347a2ec3a612c9ebc5a753db Signed-off-by: xudan <xudan16@huawei.com>
2018-05-11Adding Neutron trunk port tests to proposed_tests suiteGeorg Kunz1-0/+2
Adding the Neutron trunk port tempest tests to Dovetail and the proposed_tests test suite. JIRA: DOVETAIL-648 Change-Id: Ia77980a245fd1bca6e5f0e567467432e12bf974e Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-05-01Integrating Functest Patrole test caseGeorg Kunz1-0/+2
Adding the new Patrole test case of Functest to Dovetail and to the proposed_tests test suite. JIRA: DOVETAIL-649 Change-Id: I2c3f583cdbd3af75cec020b0fe97f287d23498a5 Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
2018-03-06leverage data_files to eliminate so many hardcoded abs_path_seekingsSerenaFeng1-0/+18
1. mv conf/ userconfig/ compliance/ patch to etc/ 2. after installation etc/ will be put under /etc/dovetail 3. leveraging /etc/dovetail in coding Change-Id: Icf9cb00ff7fc7cf35755f60d3e258b23e2c70839 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>