Test Case Template

Guidelines

Test Cases & Results

A Test Case shall have the following fields

TC ID:A unique identifier for the Test case. Enter the test case id, in ascending order.(For eg; 001,002…)

Trace Reference:Reference to the inputs for the Test case.(For eg; SRS, SDD, and Prototype etc.)

Functionality:Enter the functionality to be tested.

Pre-Condition

Test Procedure (Steps to perform):Test procedure or the steps to execute the test case

Expected Result:Expected result for the test case

TC Type:Select the TC Type for each test case from the cell drop down.

Actual Result:Actual result after execution of the test procedure .

Pass/Fail:

Bug Id:

Any event that must take place or a state that the system must be in prior to the current Test Case Scenario

Select Pass or Fail from cell drop down after verifying the actual result with the Expected result. If actual result and expected result are same, the test case should be recorded as passed for that particular round of testing

Enter the bug id (from the bug report) that is related to the test case. If there are no test cases that could be related to the bug, you can either . Modify the an appropriate test case to cover the bug detected. or . Enter a new test case

Tested By:Enter Tester's identifier as per mentioned in the test plan.

Date/Time:Enter the date and time for the test case execution. Use Ctrl + T short cut key for this.

Summary

Project Id: Enter the project's unique id.

Program Id: Unit/program/module id of the application.

Client: Enter the name of the Client of the project

Revision No:

Type of Testing:

Select the type of testing to be carried from the cell drop down.

Prepared By/ Name/Date & Time:

Reviewed By/Name/Date & Time:

Enter the name of the person, who reviewed the test cases along with the review date

Approved By/Name/Date & Time:Enter the name of the person who approved the test cases along with the approval date

Round #:Enter the Round number

Date & Time:The date of completion of that round

Tested By:The name of the user/users who executed the test cases

This indicates the number of times the test case document has been revised. Enter the Current Revision Number in sync with the Revision History sheet

Enter the name of the person, who prepared the test cases along with the start date of preparing the test cases

No of TCs:The total number of test cases

No of TCs Passed:The total number of passed test cases

Decision (Retesting Needed or Not Needed):Enter the decision whether retesting is needed or not

Remarks:Enter the remarks based upon the status of test cases.

Guidelines

Test Cases & Results

A Test Case shall have the following fields

TC ID:A unique identifier for the Test case. Enter the test case id, in ascending order.(For eg; 001,002…)

Trace Reference:Reference to the inputs for the Test case.(For eg; SRS, SDD, and Prototype etc.)

Functionality:Enter the functionality to be tested.

Pre-Condition

Test Procedure (Steps to perform):Test procedure or the steps to execute the test case

Expected Result:Expected result for the test case

TC Type:Select the TC Type for each test case from the cell drop down.

Actual Result:Actual result after execution of the test procedure .

Pass/Fail:

Bug Id:

Any event that must take place or a state that the system must be in prior to the current Test Case

Select Pass or Fail from cell drop down after verifying the actual result with the Expected result. If actual result and expected result are same, the test case should be recorded as passed for that

Enter the bug id (from the bug report) that is related to the test case. If there are no test cases that

. Modify the an appropriate test case to cover the bug detected. or

Tested By:Enter Tester's identifier as per mentioned in the test plan.

Date/Time:Enter the date and time for the test case execution. Use Ctrl + T short cut key for this.

Summary

Project Id: Enter the project's unique id.

Program Id: Unit/program/module id of the application.

Client: Enter the name of the Client of the project

Revision No:

Type of Testing:

Select the type of testing to be carried from the cell drop down.

Prepared By/ Name/Date & Time:

Reviewed By/Name/Date & Time:

Enter the name of the person, who reviewed the test cases along with the review date

Approved By/Name/Date & Time:Enter the name of the person who approved the test cases along with the approval date

Round #:Enter the Round number

Date & Time:The date of completion of that round

Tested By:The name of the user/users who executed the test cases

This indicates the number of times the test case document has been revised. Enter the Current

Enter the name of the person, who prepared the test cases along with the start date of preparing the

No of TCs:The total number of test cases

No of TCs Passed:The total number of passed test cases

Decision (Retesting Needed or Not Needed):Enter the decision whether retesting is needed or not

Remarks:Enter the remarks based upon the status of test cases.

Revision History

Document ID Proj_(Module)_TC_Ser.No.

REVISION HISTORY RECORD - PROJECTS

RevisionPrepared by:Reviewed by:Approved by:Revision Record:

Issue Rev Revised by Reviewed by Approved by

This sheet may be changed when full.

FS17-4

REVISION HISTORY RECORD - PROJECTS

Revision Record:Effective Date

FD07-1

Section(s) Affected in This Revision.

Template id: FFS17-3 Page 11 of 25 document.xls

TC Id Trace Reference Functionality Pre-Condition

Guidelines


Test Case & Result

Test Procedure (Steps to perform) Expected Result TC Type


Round 1

Actual Result Pass/Fail Bug Id Tested By Date & Time

L7

Press Ctrl+T to insert Currrent Date & Time


Round 2

Actual Result Pass/Fail Bug Id Tested By Date & Time Actual Result Pass/Fail

Q7



Round 3 Round 4

Bug Id Tested By Date & Time Actual Result Pass/Fail Bug Id

V7



Round 5

Tested By Actual Result Pass/Fail Bug Id Tested By Date & TimeDate & Time

AA7


AF7



TC Id Trace Reference Functionality Pre-Condition

Guidelines


Test Case & Result

Test Procedure (Steps to perform) Expected Result TC Type


Round 1


L7



Round 2


Q7



Round 3

Actual Result Pass/Fail Bug Id Tested By Date & Time Actual Result

V7



Round 4 Round 5

Pass/Fail Bug Id Tested By Date & Time Actual Result Pass/Fail Bug Id Tested By

AA7



Date & Time

AF7



Summary

Project Id:Program Id:Client:Revision No.:Type of testing:

Name Date & TimePrepared By:Reviewed By:Approved By:

Note: While adding new sheets, include new rows and modify the formula accordingly

Sheet Name Date & Time Tested By No. of TCs0 00 0

Guidelines

No : of Test cases Executed


Remarks0 0 0 0 00 0 0 0 0

No. of TCs Passed in !st Round

No. of TCs Passed in 2nd Round

No. of TCs Passed in 3rd Round

No. of TCs Passed in 4th Round

No. of TCs Passed in 5 th Round

Decision (Retesting Needed/Not Needed)

Documents

Test Case Template