Sie sind auf Seite 1von 25

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,00 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 Any event that must take place or a state that the system must be in prior to the current T Scenario 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:

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

Enter the bug id (from the bug report) that is related to the test case. If there are no test c 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: This indicates the number of times the test case document has been revised. Enter the Revision Number in sync with the Revision History sheet Type of Testing: Select the type of testing to be carried from the cell drop down. Prepared By/ Name/Date & Time:

Enter the name of the person, who prepared the test cases along with the start date of prep test cases 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

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.

owing fields

ascending order.(For eg; 001,002)

and Prototype etc.)

must be in prior to the current Test Case

n.

actual result with the Expected result. If should be recorded as passed for that

test case. If there are no test cases that

ed. or

+ T short cut key for this.

ent has been revised. Enter the Current

n.

along with the start date of preparing the

ong with the review date

ong with the approval date

Revision History

Document ID Proj_(Module)_TC_Ser.No.

REVISION HISTORY RECORD - PROJECTS Revision Prepared by: Reviewed by: Approved by: Revision Record: Rev Revised by

Issue

Reviewed by

Approved by

This sheet may be changed when full.

FS17-4

D - PROJECTS

Section(s) Effective Date Affected in This Revision.

FD07-1

Guidelines TC Id Trace Reference Functionality Pre-Condition

Template id: FFS17-3

Page 11 of 25

60698254.xls

Test Case & Result

Test Procedure (Steps to perform)

Expected Result

TC Type

Template id: FFS17-3

Page 12 of 25

60698254.xls

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

Template id: FFS17-3

Page 13 of 25

60698254.xls

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

Template id: FFS17-3

Page 14 of 25

60698254.xls

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

Round 4 Bug Id

Template id: FFS17-3

Page 15 of 25

60698254.xls

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

Template id: FFS17-3

Page 16 of 25

60698254.xls

Guidelines TC Id Trace Reference Functionality Pre-Condition

Template id: FFS17-3

Page 17 of 25

60698254.xls

Test Case & Result

Test Procedure (Steps to perform)

Expected Result

TC Type

Template id: FFS17-3

Page 18 of 25

60698254.xls

Actual Result

Pass/Fail

Round 1 Bug Id

Tested By

Date & Time

Template id: FFS17-3

Page 19 of 25

60698254.xls

Actual Result

Pass/Fail

Round 2 Bug Id

Tested By

Date & Time

Template id: FFS17-3

Page 20 of 25

60698254.xls

Actual Result

Pass/Fail

Round 3 Bug Id

Tested By

Date & Time

Actual Result

Template id: FFS17-3

Page 21 of 25

60698254.xls

Pass/Fail

Round 4 Bug Id

Tested By

Date & Time

Actual Result

Pass/Fail

Round 5 Bug Id

Tested By

Template id: FFS17-3

Page 22 of 25

60698254.xls

Date & Time

Template id: FFS17-3

Page 23 of 25

60698254.xls

Summary
Guidelines Project Id: Program Id: Client: Revision No.: Type of testing: Name Prepared By: Reviewed By: Approved By: Note: While adding new sheets, include new rows and modify the formula accordingly Date & Time

Sheet Name

Date & Time

Tested By

No. of TCs 0 0

No : of Test cases Executed 0 0

Template id: FFS17-3

Page 24 of 25

60698254.xls

Decision No. of TCs No. of TCs No. of TCs (Retesting No. of TCs Passed in ! No. of TCs Passed in 2nd Passed in Passed in Passed in Needed/Not st Round Round 3rd Round 4th Round 5 th Round Needed) Remarks 0 0 0 0 0 0 0 0 0 0

Template id: FFS17-3

Page 25 of 25

60698254.xls

Das könnte Ihnen auch gefallen