THE GUIDE LINES TO BE FOLLOWED BY A TEST ENGINEER, SOON AFTER THE USE CASE DOCUMENT IS RECEIVED

1. Identify the module to which the use case belongs to.

 A: Security module.

2. Identify the functionality of the use case with the request of total functionality.

 A: Authentication.

3. Identify the actors involved in the use case.

A: Normal user/Admin user.

 4. Identify the inputs required for testing.

A: Valid and invalid user names and passwords.

 5. Identify whether the use case is linked with other use case or not.

 A: It is linked with Home page and Admin page use cases.

 6. Identify the pre conditions.

A: LOGIN Screen must be available.

7. Identify the post conditions.

A: Either Home page/Admin page for valid users, and error msgs for invalid users.

 8. Identify the functional points and prepare the functional point document.

UNDERSTAND:

9. Understand the main flow of the application.

10. Understand the alternative flow of the application.

11. Understand the special requirements.

 DOCUMENT:

12. Document the test cases for main flow.

13. Document the test cases for alternative flow.

14. Document the test cases for the special requirements.

15. Prepare the cross reference metrics or traceability metrics.

 

Functional Point: The point at which the user can perform some actions in the application can be considered as Functional Point.

Test Scenario: The situation where we can do testing.

There are 3 types of flow:

1. Main flow: Main page/Home Page.

2. Alternative flow: Error message page.

3. Exceptional flow: Server problems/Network problems.

Testing process related Documents: