summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristopherPrice <christopher.price@ericsson.com>2017-05-07 13:44:39 +0200
committerChristopherPrice <christopher.price@ericsson.com>2017-05-07 13:44:39 +0200
commit3bb2ec53f6870b1ee9148532405573ce7624300e (patch)
tree251fee31d83ee6f1a9acf7f2aa93f56da654bd5e
parenta1c406955bdc44e714a002c9623559b0e5d9ec56 (diff)
Proposing to move "post conditions" as an optional topic for a test case.
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>
-rw-r--r--docs/testing/developer/testcaserequirements/index.rst14
1 files changed, 2 insertions, 12 deletions
diff --git a/docs/testing/developer/testcaserequirements/index.rst b/docs/testing/developer/testcaserequirements/index.rst
index 5dc87713..38eb93a1 100644
--- a/docs/testing/developer/testcaserequirements/index.rst
+++ b/docs/testing/developer/testcaserequirements/index.rst
@@ -9,17 +9,6 @@ Compliance and Verification program test case requirements
.. toctree::
:maxdepth: 2
-Version history
-===============
-
-+------------+----------+------------------+----------------------------------+
-| **Date** | **Ver.** | **Author** | **Comment** |
-| | | | |
-+------------+----------+------------------+----------------------------------+
-| 2017-03-15 | 0.0.1 | Chris Price | Draft version |
-| | | | |
-+------------+----------+------------------+----------------------------------+
-
CVP Test Suite Purpose and Goals
================================
@@ -69,12 +58,13 @@ The following requirements are mandatory for test to be submitted for considerat
- Use case specification
- Test preconditions
- Basic test flow execution descriptor
- - Post conditions and pass fail criteria
+ - Pass fail criteria
- The following things may be documented for the test case:
- Parameter border test cases descriptions
- Fault/Error test case descriptions
+ - Post conditions where the system state may be left changed after completion
New test case proposals should complete a CVP test case worksheet to ensure that all
of these considerations are met before the test case is approved for inclusion in the