Explanation of different sections in a Test Case Template
Change History: Under this section, you specify, who changed what in the document and when, along with the version of the document which contain the changes.
Review and Approval History: This captures who reviewed the document and whether they Approved the test case or not. If approved, the reviewer will specify the review comments to be incorporated in the test case.There is a review template at the end of the template document, which can be used to specify the comments.If the test case document is ‘Not Approved’, then either the test case is not necessary(redundant) or it is in a very bad shape(not in a state to be reviewed)
Document References: Any additional documents that will help better understand the test case like test oulines or design documents or Requirements document etc.
Introduction/Overall Test Objectives: Specify at a very high level, what the test case is intended to achieve or verify.
Test Case Limitations: Does the test case achieve the above mentioned test objective completely or are there any exceptions?These exceptions need to be specified in this section.For example, test case has to verify something on type A, type B and type X, but because of some reason it could NOT verify that something on type X, then its a limitation.
Test Case Dependencies / Assumptions: Prior to executing this test case, any other test case needs to be run? All those dependencies need to mentioned here.
Setup Requirements: Any setup that has to be done in the application being tested, prior to executing this test script should be mentioned here.For example, if the test case needs certain Login IDs with certain settings to begin, which are not created as part of the test case, then such things need to mentioned in this section
Process Flow: In this section, we mention who does what in the test case. Suppose there are multiple users in the test case, then a process flow can look like
user1: does something
user2: does something else
user1: does again something
user2: says good bye
Test Case: The actual test case begins in section 5, which can be further divided into subsections upon convenience and need.For example, if the test case is for an integrated application, then everytime we login to a new application, we can have a new subsection. Following is the example of how a test case looks like
- Step Num: 1
- Step Description: check login
- Path and Action: Enter user name, Enter pwd, click Login
- Test Data: abcd, abcd
- Expected Results: Verify error message is thrown that username and password entered are wrong
Appendix: This section contain any additional data that the test case refers.For example if your test case has large amounts of ‘Test Data’ which is difficult to put under the column ‘Test Data’ for each step, then you can use the appendix section to hold the data and in the test case, can give reference to appendix.
Test Case Review Template: This template can be used by the reviewers to provide their review comments.They can classify the comments based on their severity.The Test Engineer who incorporates the comments in the test case, should specify the action taken by him in the template and then ‘Close’ the comment.