Age | Commit message (Collapse) | Author | Files | Lines |
|
This patchset addresses review comments which were not incorporated in
the previous version of the test case requirements description.
Additionally, the text has been wrapped to 80 character lines.
Change-Id: If817f6c44d94870d915791a1a11916ffe4871f06
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
And additional clarifications.
JIRA: DOVETAIL-477
Replace tabs.
Further clarify testing programs and optionality criteria.
Change-Id: I8eebdf215fb7cc75a6da9748629b1a73d0b71d19
Signed-off-by: Bryan Sullivan <bryan.sullivan@att.com>
|
|
It is not clear that there are post conditions to be documented for all test cases.
In the case a test cse creates an image and deletes it, there is littöe need for
a post condition to be documented. If a test case establishes a network to be
used for a subsequent test ina sequence this information should be clearly dcumented.
Change-Id: Ifb4bb45f240921c180077ab7273988d973417f6f
Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
|
|
This doucment needs to be +2'd by the majority of committers prior to merging
to ensure we are all in agreement with regard to the test case requirements.
This is a pre-requisite to test case selection for the CVP.
Updated by dneary 2017-04-25: List formatting, and reorganising requirements for installer and stack composition.
Change-Id: Iabaf11bc9479a20a58f985233d460013e4690d7c
Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
|