Scribd
Upload
201 views

Test Case Template

This document provides a template for writing test cases with fields for the test case ID, name of the tester who designed it, design and execution dates, test title, summary, pre-conditions, dependencies, steps, expected and actual results, status, and additional optional fields like attachments. The template includes guidance on how to structure test case IDs and provides example field values.

Uploaded by

Marijana Ničić
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
201 views

Test Case Template

This document provides a template for writing test cases with fields for the test case ID, name of the tester who designed it, design and execution dates, test title, summary, pre-conditions, dependencies, steps, expected and actual results, status, and additional optional fields like attachments. The template includes guidance on how to structure test case IDs and provides example field values.

Uploaded by

Marijana Ničić
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Test Case template

Test case ID: Unique ID is required for each test case. Follow some convention to indicate
the types of the test. For Example, ‘TC_UI_1' indicating ‘user interface test case #1'.
Test Designed By Name of the Tester.
Test Designed Date: Date when it was written.
Test Execution Date: Date when the test was executed.
Test Title/Name: Test case title. For Example, verify the login page with a valid username
and password.
Test Summary/Description: Describe the test objective in brief.
Pre-conditions: Any prerequisite that must be fulfilled before the execution of this test
case. List all the pre-conditions in order to execute this test case successfully.
Dependencies: Mention any dependencies on the other test cases or test requirements.
Test Steps: List all the test execution steps in detail. Write test steps in the order in which
they should be executed. Make sure to provide as many details as you can.
Pro Tip: In order to manage a test case efficiently with a lesser number of fields use this
field to describe the test conditions, test data and user roles for running the test.
Test Data: Use of test data as an input for this test case. You can provide different data
sets with exact values to be used as an input.
Expected Result: What should be the system output after test execution? Describe the
expected result in detail including message/error that should be displayed on the screen.
Post-condition: What should be the state of the system after executing this test case?
Actual result: The actual test result should be filled after test execution. Describe the
system behavior after test execution.
Status (Pass/Fail): If an actual result is not as per the expected result, then mark this test
as failed. Otherwise, update it as passed.
Notes/Comments/Questions: If there are some special conditions to support the above
fields, which can’t be described above or if there are any questions related to expected or
actual results then mention them here.
Add the following fields if necessary:

Defect ID/Link: If the test status is failed, then include the link to the defect log or mention
the defect number.
Test Type/Keywords: This field can be used to classify the tests based on test types. For
Example, functional, usability, business rules, etc.
Requirements: Requirements for which this test case is being written for. Preferably the
exact section number of the requirement doc.
Attachments/References: This field is useful for complex test scenarios in order to explain
the test steps or expected results using a Visio diagram as a reference. Provide the link or
location to the actual path of the diagram or document.
Automation? (Yes/No): Whether this test case is automated or not. It is useful to track the
automation status when test cases are automated.

You might also like