Normally when we prepare test cases for a web based application following areas are covered:
1. Functionality
2. UI look & feel
3. Security
4. Performance
5. Data verification
Suppose we want to test a login feature for www.gmail.com then following details should be associated with the test cases:
1. Test Case Name/Id - this can be unique identifier for test case.
E.g.: BankApp_Login_01
2. Test Case Description/Overview/Purpose - 1 liner description of the test case what it is suppose to check for
E.g.: Purpose of this test cases is to verify that an authenticated user can login to the application
3. Design steps: Detailed steps to be performed while testing any feature
E.g. : a) Connect to the site .. www.gmail.com
b) Enter user name and password… testuser/password
4. Expected behavior for each test case/step
E.g. a) Login page of the www.gmail.com should be displayed
b) User should be able to login with the credentials testuser/password and see home page
5. Actual result for each test case/step after execution
E.g.: a) Login page displays when connect to the web site www.gmail.com
b) testuser is able to see the home page
6. Status of test case: Pass/Fail based on actual result
E.g. In this case as actual result is as same as expected behavior so status would be ‘Pass’, else it would be ‘Fail’
7. Test Case Category: Whether it’s a functional/sanity/performance/regression/data test case
E.g.: This particular functionality of login would be sanity category…as this application can’t be tested without this feature working fine
8. Automation Candidate: If automation is to be done for the application then whether this feature can/should be automated? This requires inputs from automation team as well. In this example this test case is the entry point to the application and hence should be automated.
9. Priority of execution: Decided based on the importance of the feature. High priority test cases should be executed first as soon as build is released to QA to make sure that the build is testable or not. Like E.g. exporting data to different formats would be high priority feature than the minor look & feel.
E.g.: this test case is P1…unless and until this working fine…testing can’t be carried out
10. Comments: Extra comments if you want to put like…bug id for the failed testcase.
For now I can recall these details…get back if you need more.
Regards,
mbalajiwale_InfoCepts
www.inforcepts.com
