| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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>
|
|
Spliting the IPv6 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-677
Change-Id: If3dca5ecf2ce5c9e02de5c6d45e674da029b609f
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
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>
|
xudan
Georg Kunz