• info@helpingtesters.com
  • helpingtesters

Test Case Writing Sample Template

Software Testing Templates
Test Case Writing sample template

Test Case writing is an integral task of every testing team. Be it automation or manual, every testing team creates test cases to map different client scenarios to the test cases. Every test case contains details of the test, the expected output along with the various other components. This Test Case Writing sample template gives an idea of what all has to be documented while designing test case documents.

In this article, we would share with you a dummy test case template which you can use to create test cases on your own. To explain the different components in detail, we would create test cases for some basic functionalities of HelpingTesters. So let’s start with the significance of test case writing, followed by the different components in the Test Case Writing Sample Template.

Test Case Sample Template

HelpingTesters Test Case Sample Template

Why are Test Cases important?

Many testers find test case writing a tedious task. While creating the test cases the testing team must ensure that all the tests for a scenario are covered and all steps and expected conditions are clearly mentioned. But why write test cases?

  • Test Cases are mostly written during the design phase/ development phase when developers are still working on the application.
  • Well documented test cases are used to thoroughly test the application. The test description and test steps allow other testers from different teams or new testers to understand the test scenario and execute it on their own.
  • Test Cases, once written are reviewed so that any and all ambiguities are eliminated. This ensures all functionalities are properly replicated in tests.
  • Test Cases which fail often help testers find out the modules of the application which are more prone to bugs. These test cases are used to report issues. Another way of putting it is, test cases help structure test case execution and reduce ad-hoc or monkey testing.
  • When developers are busy coding, the testing team goes through the application requirement document and create the test cases. These test cases are created using the CRD alone and are not influenced by the understanding of the developers. Such isolation while creating test cases improves the quality of the product.

While creating the test cases, you must make sure that they are easy to read and understand. Also, to ensure the authenticity and quality of the test cases, they must be verified/ reviewed by the test lead. Once verified the test cases are pushed into one or the other test case management tool so that all members of the testing team can access and execute them.

What are the different components of a test case writing sample template?

Now that you are aware of the importance of test cases, you must understand different components of the test case template. Test case templates sometimes are shared by the company so that all test cases of a particular project or across the company adheres to a specific standard. But in many cases, you can come up with a template of your own. The test case template should be such that it is easy to edit and maintain. Here we will discuss the test case components for any of the Test Case Writing Sample Template. So, the primary components of the Test Case Writing Sample Template can be basically divided into 2 sections, namely.

Figure 1: Test Case Summary section

Test Case Summary 

As the test cases are mostly curated in spreadsheets or in Excel format, the test case summary is ideally the first sheet of the test case template. The different sections in the summary section are

  • Company Logo – It is the logo of the company or the project for which you are writing the test cases. The logo is provided to give it a professional feel and sometimes to meet the company policy or standard.
  • Project & module name – Project name is a mandatory component and must be included in the summary section. In case of big projects, where different modules are handled by separate QA teams, module name also needs to be specified along with project name.
  • Release version – With every release, as new functionalities are added, the existing test cases must also be updated. So, different versions are assigned to different releases. The release version indicates the test cases that are specific to a particular release.
  • Test Design authors – Depending on the scale of the project the test cases can range from a handful to a few hundred. As all the test cases can’t be designed by a single tester, multiple testers work on test case design. In the test case author section, the name of the testers responsible for the test case design is included.
  • Test Case design date – The test case design date tells the date when the current version of the test cases was completed.
  • Test Executed By and test execution date – As the name suggests, in this field, the name of the testers who executed the test cases are mentioned along with the last execution date.

Figure 2: Different application modules

Test Modules

After the test summary, we have the different test case modules. These test modules are maintained in different sheets, and all test cases specific to a certain module are listed in that very sheet. For example, all test cases for application login would be maintained in the login module, while all the test cases for personalized dashboard would be logged in a separate dashboard module. So, when the design phase is completed, all test cases from different application modules should be present in different sheets in the same excel or spreadsheet. Such a way of grouping test cases helps other fellow testers to easily track test cases. The important components of test cases are:

Figure 3: Test Case components

  • Test Case id – It is the specific ID, provided to every test case. The test case ID must be unique, and should ideally follow a naming convention. Generally, testers provide meaningful names to the test case ids, so that their purpose can be easily known. For example, TC_01_HelpingTesters_valid_login.
  • Test Title – The test title tells you the intent of the test case. Mostly testers use the test title and append some id to get the test case id. An example of a proper test title would be, “HelpingTesters valid login”.
  • Test Summary – The test summary outlines the objective of the test case. It briefly states the preconditions required to execute the test case and what result would be obtained. Any additional notes can also be mentioned in this section.
  • Test Steps – The test steps are one of the most important components of a test case. The test steps tell testers who are executing the test case, which steps to follow to execute a specific step. Test steps are generally listed in multiple lines.
  • Expected Result – Corresponding to every test step written for a test case, an expected result is written. The expected result shows what a tester should expect while executing a certain test step.
  • Actual Result – After executing each test step, the actual result should be mentioned here. The actual result may or may not be the same as the expected result. The actual result fields for the test cases are filled during test execution.
  • Status – This field captures the current condition of a test step. Test status can either be “Not Run”, “Not Completed”, “Pass”, or “Fail”. During test execution if the expected result and the actual result of a test step doesn’t match, the status should be set as “Fail”, and if they do, the test step should be marked as “Pass”. The status field too is filled by the testers during test execution. Many testers prefer putting different color schemes for different statuses. Red for “Fail, Green for “Pass”, Orange for “Not Completed” and Blue for “Not Run”.
  • Notes – This is an optional field. Many testers even name it as “Comments” section. Any specific comment or note about any test step or test case as a whole can be listed in this section.

Now the question is how does the Test Case Writing Sample Template look. To a get a better understanding of the topic, we have put together a dummy Test Case Template which you can refer to for your study purposes or use it in your projects. You can download it for free, HERE. Along with that, we have shared a Test Case Template for some of our application modules at HelpingTesters. You can download it for free, HERE.

Download Test Case Writing Sample Template below:

Test Case Sample Template

HelpingTesters Test Case Sample Template


  • You must choose your test case template properly. The template should contain the important components while fulfilling the project parameters.
  • The test summary section should provide the overall details of the test case template.
  • Test Cases for different modules can be saved in different sheets. Each sheet would contain the test cases specific to that particular module, along with their status.
  • With every release, the test case template needs to updated.
  • The test cases should be maintained every time a new functionality is added or an existing one is changed.
  • The verbose and style of writing should be easy to understand and should not be extremely technical.
  • Once the test cases are reviewed by the lead, they can be uploaded to test case management tool.

It is very important to set the standard Test Case Writing Sample Template in any of the projects and should be made mandatory to use the same. Doing this helps in achieving the uniformity of the entire regression suite.

About the author

arindam bandyopadhyay author

Arindam Bandyopadhyay is an automation tester with over 5 years of experience in software testing. While during the day he juggles between Eclipse and spreadsheets, at night he lets his fingers do the talking as he writes about anything and everything his paradoxical mind desires.

Leave a Reply

Your email address will not be published.