summaryrefslogtreecommitdiffstats
path: root/etc/testcase/tempest.vm_lifecycle.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-07-30Dovetail failed to archive tempest.log and tempest-report.html filesxudan1-2/+2
It failed to archive tempest.log and tempest-report.html files. See CI results https://build.opnfv.org/ci/view/dovetail/job/dovetail-compass-baremetal-default-mandatory-fraser/7/artifact/results/ That's because the path of them have been changed 1. from tempest to tempest_custom 2. from refstack to refstack_defcore There seems to be no file bgpvpn.log, remove the copy operation. JIRA: DOVETAIL-714 Change-Id: I77d88124a44d3e5d869ada209760f69d1f6553bf Signed-off-by: xudan <xudan16@huawei.com>
2018-05-27Archive all test case result filesxudan1-0/+9
1. All detailed tempest test cases results are recorded with file tempest-report.html rather than tempest.log now. 2. Archive all results files include functest.log, yardstick.log ... for each test case. Otherwise, they will all be in one log file. 3. Support to set the source files and dest files need to be archived with the test case config files rather than hardcode with the source code. 4. Give the file which used to be parse the results (PASS/FAIL) with the test case config files rather than hardcode with the source code. Change-Id: I30f435d91ab90cf20def47007f177fe98187484d Signed-off-by: xudan <xudan16@huawei.com>
2018-05-18Correct the names of sub test cases due to the new Tempest versionxudan1-10/+10
1. Change from Functest Danube to Fraser, the Tempest version it integrates is from 14.0.0 to 17.1.0. 2. Some sub test cases names have been changed. 3. Some are removed from tempest_smoke. 4. Some are new added into tempest_smoke. JIRA: DOVETAIL-657 Change-Id: Ie5611f5b7a5888bea3942667907341bd071d399d Signed-off-by: xudan <xudan16@huawei.com>
2018-05-15Renaming test cases for better readabilityGeorg Kunz1-0/+27
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>