Sample Test Case Template with Test Case Examples [Download]

Every day, I receive a multitude of requests for a Test Case Template. Many testers perplexingly continue to use Word documents or Excel files to record their test cases, much to my surprise.

Excel spreadsheets are favored by many testers as they allow for test cases to be grouped by type and for test metrics to be computed using Excel formulas. However, when the quantity of tests grows, their management becomes increasingly burdensome.

If you haven’t already implemented a Test Case Management tool, I would strongly advise employing an open-source tool to organize and carry out your test cases.

Though test case formats vary across different organizations, employing a standardized format is a vital step towards establishing a testing process for your project.

This also decreases unplanned testing without the appropriate test case documentation. Although standard templates are useful, manual processes are still needed for creating, reviewing, and approving test cases, as well as preparing test execution and test reports.

If your test cases need to be evaluated by the business team, using a mutually agreed upon template is crucial.

Preferred Tools

Before beginning the process of writing test cases, I advise downloading these test case management tools. These will make the test planning and test case writing procedures mentioned in this tutorial more straightforward.

#1) TestRail

=> Get TestRail Test Case Management Tool

#2) Katalon Studio

Katalon Studio is a one-stop automation tool for web, API, mobile, and desktop testing that over 850,000 users trust.

It makes automation easier for non-technical users by providing a diverse library of project templates, record & playback functionality, and a user-friendly interface.

=> Begin for Free

#3) TestMonitor

TestMonitor is an advanced online test management tool that offers a fresh and simple approach to testing.

It offers a complete test management solution for every company, simplifying testing for enterprise software, quality app development, and test projects.

=> Visit TestMonitor Website

Let’s simplify the manual test case management process a bit by using simple testing templates.

Take Note: I have listed all the fields related to the test case. However, I recommend that you only use the fields relevant to your team. If any fields used by your team are missing from this list, feel free to add them to your personalized template.

Standard Fields of a Sample Test Case Template

Certain standard fields should be taken into account when making a test case template.

Here are standard fields for a sample test case template:

#1) Test case ID: Each test case needs a unique ID. Use conventions to signify the types of tests. For instance, ‘TC_UI_1’ denotes ‘user interface test case #1’.

#2) Test priority (Low/Medium/High): Test priority is useful during test execution. Business rules and functional test cases can have a medium or high priority, while less critical user interface cases can have a low priority. Test priorities should be determined by reviewers.

#3) Module Name: Mention the name of the main module or sub-module.

#4) Test Designed By: The name of the tester who created the test.

#5) Test Designed Date: The date the test was composed.

#6) Test Executed By: The name of the tester who performed the test. Fill in this field only after test execution.

#7) Test Execution Date: The date the test was conducted.

#8) Test Title/Name: Title of the test case. An example would be, “Verify login page with valid username and password”.

#9) Test Summary/Description: A brief description of the test’s aim.

#10) Pre-conditions: Any conditions that must be met before executing this test case. List all the preconditions required for a successful test execution.

#11) Dependencies: Note any dependencies on other test cases or test requisites.

#12) Test Steps: Detail the steps for test execution. Write them in the order they should be performed. The more detail, the better.

#13) Test Data: Utilize test data as input for this test case. Provide multiple data sets with specific values to be used as input.

#14) Expected Result: Describe what the system output should be after performing the test. Include detailed information, including any messages or errors that should be displayed on the screen.

#15) Post-condition: Describe what the state of the system should be after the execution of this test case.

#16) Actual Result: Fill in the real test result after executing the test. Describe the system’s behavior after the test is conducted.

#17) Status (Pass/Fail): If the real result is not the same as the expected result, designate the test as “failed”. Otherwise, update it as “passed”.

#18) Notes/Comments/Questions: Use this field for any unusual conditions related to the previously mentioned fields. If there are any uncertainties about expected or actual results, note them here.

If necessary, add the following fields:

#19) Defect ID/Link: If the test status is “failed”, include the link to the defect log or mention the defect number.

#20) Test Type/Keywords: Use this field to classify tests into categories like functional, usability, or business rules.

#21) Requirements: Specify the requirements for which this test case is written. Ideally, include the section number in the requirement document.

#22) Attachments/References: Use this field to attach or reference any diagrams or documents that outline test steps or expected results for intricate test scenarios.

#23) Automation? (Yes/No): Specify whether this test case is automated or not. This is useful for tracking the automation status of test cases.