Process Cycle Test
Procedure for the Process Cycle Test (automated)
Use Cases Testing: The steps to be taken in order to arrive at a automated specification for a process cycle test include:
See also: Procedure for the Process Cycle Test (manually)
- Establishing/data entry path combinations.
COVER generates test cases (test depth 1 and 2).
- Establishing the initial data set.
- Assembling the test script.
Establishing path combinations
For every decision point found, the path combinations must be determined. A path combination is a link between an action before a decision point and an action after the same decision point. When creating path combinations, it is wise to number the actions first. Sequential actions between two decision points receive a common number. All path combinations, i.e. all combinations of two consecutive actions with a decision point in between, must be written out. This is illustrated in the following example:
fig.2 Activity Diagram of the Use Case: Manage Courses
In the course administration department, modification forms come in concerning self made and/or bougth courses. The head of the department receives the modification forms and passes them on to an employee of the department. Depending on the type of modification (changing, entering or deleting) a maintenance function for the course data is started. After the modification has been performed, the next form is executed. After performing all the forms, the employee provides the head of the department with a written report of completion.
Path combinations for decision point A: (1,2); (1,3); (7,2); (7,3);
Path combinations for decision point B: (3,4) and (3,5);
Path combinations for decision point C: (2,6); (4,6); (5,6); (2,7); (4,7); (5,7);
Quick-start: Data entry path combinations
COVER has a Quick-start possibility. Op base of only the above path combinations,COVER can generate the test paths for test measure 1 and test measure 2
After the data-entry of the path combinations of the decision points A,B and C COVER delivers this output in a (zipped) RTF-file by sending it to your e-mail adress.
COVER: Specifying test cases
When the path combinations during data entry are expanded with the description of the Use Case actions, Cover can use this information to specify the test cases.
This RTF-file contains an example of specified test cases.
COVER: PCT for experienced users
In complex Use Cases situations may occur that path combinations conflict with each other. A decision in the beginning of the Use Case can be repeated in more or less the same form at the end of the use case. In that case COVER gives the possibility of exclusion of path combinations.
Because (re-)generating can be done in no time, this functionality can also be used in case of partially released software.
During data-entry the conflicting paths are entered in the field "Conflicting or not yet released paths".
Assembling the testscript
See the TMap®-book.
Testuitvoering en beoordeling
See the TMap®-book.