Hello friends! In this post we will present a test case template in excel/spreadsheet, describing the use of each field in detail. Ideally, a test case management tool should be used for managing the test cases and test execution cycles. But for smaller projects, many organizations still prefer to use spreadsheets for avoiding the overhead of maintaining and configuring a tool.
Now we will see the different fields of a test case – mandatory as well optional.
- TestCaseId – This field uniquely identifies a test case. It is mapped with automation scripts(if any) to keep a track of automation status. The same field can be used for mapping with the test scenarios for generating a traceability matrix. E.g. – GoogleSearch_1
- Component/Module – This field specifies the specific component or module that the test case belongs to. E.g. – Search_Bar_Module
- Priority – This field is used to specify the priority of the test case. Normally the conventional followed for specifying the priority is either High, Medium, Low or P0, P1, P3, P3, etc with P0 being the most critical.
- Description – In this field describe the test case in brief. E.g. – Verify that when a user writes a search term and presses enter, search results should be displayed.
- Pre-requisites – In this field specify the conditions or steps that must be followed before the test steps executions. E.g. – Browser is launched.
- Test Steps – In this field, we mention each and every step for performing the test case. The test steps should be clear and unambiguous. E.g.
- Write the URL – http://google.com in the browser’s URL bar and press enter.
- Once google.com is launched, write the search term – “Apple” in the google search bar.
- Press enter.
- TestData – In this field, we specify the test data used in the test steps. E.g. in the above test step example we could use the search term-“apple” as test data.
- Expected Result – This step marks the expected result after the test step execution. This used to assert the test case. E.g. – search results related to ‘apple’ should be displayed.
- Actual Result – In this step, we specify the actual result after the test step execution. E.g. – search results with ‘apple’ keyword were displayed.
- Status/Test Result – In this step, we mark the test case as pass or fail based on the expected and actual result. Possible values can be – Pass, Fail, Not executed.
- Test Executed by – In this field we specify the tester’s name who executed the test case and marked the test case as pass or fail.
Apart from these mandatory fields, there are many optional fields that can be added as the organization or application’s need like Automation status – for marking test as automated or manual, TestScenarioId – for mapping test case with its test scenario, AfterTest step – for specifying any step required to be executed after performing the test case and TestType – to specify if the test is applicable for Regression, Sanity, Smoke, etc and DefectId – id of the defect launched in any of the defect management tools, etc.
Apart from these some other fields can be added for additional information like – Test Author, Test Designed Date, Test Executed Date, etc.
Now you can download the test case template from here – TestCaseTemplate.xlsx. Along with the template we have provided a sample test case for your reference. The template is provided as xlsx, you can format the template as per your requirement.
That’s all I have in this section, please let me know in the comments if you have any questions. Also, check our complete software testing tutorial here.
Kuldeep is the founder and lead author of ArtOfTesting. He is skilled in test automation, performance testing, big data, and CI-CD. He brings his decade of experience to his current role where he is dedicated to educating the QA professionals. You can find him on LinkedIn.