Use cases based test case design: -
In some situations, the testing team converts functional & system specifications in SRS into use cases to maintain complete & correct information. This is possible to outsourcing testing organizations. In this method, test engineers prepare test cases depending on use cases instead of functional & system specifications.
Use cases are more elaborate than functional & System specifications in SRS. Every use case follows a common format.
Use cases are more elaborate than functional & System specifications in SRS. Every use case follows a common format.
Use Case Format:
1. Use case Id: Unique no. or name for future reference.
2. Use case description: The summary of use case functionality
3. Actors: The input requirements of corresponding functionality
4. Pre-Conditions: Necessary tasks before starting this functionality
5. Actions: A step-by-step procedure with required inputs and expected outputs
6. Post-Conditions: Necessary tasks after completion of this functionality
7. Alternative flows: a step-by-step alternative procedure if possible.
8. Flow Graph: Diagrammatic notation to understand functionality.
9. Prototype: Model screen to understand functionality
10.Exceptions or Rules: The possible conditions in that functionality if available.
After completion of all reasonable use cases development with complete & correct information, the separate testing team concentrates on test case selection & documentation.
1. Collect required use cases and their dependencies.
2. Select on use case from the list
3. Study the use case in terms of inputs, base state, end state, outputs, normal flow, alternative flow and Rules.
4. Prepare test vase titles or scenarios.
5. Review the titles for completeness & correctness.
6. Document the test cases with complete information.
7. Go to step 2 until all collected use cases are studied.
NOTE:
1. The functional & System specification based test case design is suitable for general organizations because subject exploring is possible in general organizations. The use cases based test case design is suitable for testing outsourcing companies because subject exploring is critical for them.
2. First method is suitable for applications where as the second method is more suitable for product based organizations.
2. Use case description: The summary of use case functionality
3. Actors: The input requirements of corresponding functionality
4. Pre-Conditions: Necessary tasks before starting this functionality
5. Actions: A step-by-step procedure with required inputs and expected outputs
6. Post-Conditions: Necessary tasks after completion of this functionality
7. Alternative flows: a step-by-step alternative procedure if possible.
8. Flow Graph: Diagrammatic notation to understand functionality.
9. Prototype: Model screen to understand functionality
10.Exceptions or Rules: The possible conditions in that functionality if available.
After completion of all reasonable use cases development with complete & correct information, the separate testing team concentrates on test case selection & documentation.
1. Collect required use cases and their dependencies.
2. Select on use case from the list
3. Study the use case in terms of inputs, base state, end state, outputs, normal flow, alternative flow and Rules.
4. Prepare test vase titles or scenarios.
5. Review the titles for completeness & correctness.
6. Document the test cases with complete information.
7. Go to step 2 until all collected use cases are studied.
NOTE:
1. The functional & System specification based test case design is suitable for general organizations because subject exploring is possible in general organizations. The use cases based test case design is suitable for testing outsourcing companies because subject exploring is critical for them.
2. First method is suitable for applications where as the second method is more suitable for product based organizations.
No comments:
Post a Comment