Testing is an important part of the software development process. We must consider the following artefacts while doing quality testing: Software Specification, Test Plan, Test Case, Test Suite, Bug Reports, and Checklists.
In this article, we’ll look at one of the most important artefacts: the test case.
1. What is the test case?
A test case is a document that contains a set of test data, preconditions, expected outcomes, and postconditions that were created for a specific test scenario in order to check compliance with a certain requirement.
Those entail creating test cases that span a wide range of program features. It also entails developing test cases in a clear and efficient manner, as a bad test might be more harmful than beneficial.
A test suite is a collection of test cases that are arranged to test a logical portion of the program, such as a single feature.
2. Test Case Attributes
2.1 TestCase ID
It is the unique ID of the test case which is used as a unique identifier for the test case. For e.g., TC_01
2.2 Test Case Name
Test Case Name is written as a combination of User Story ID_ User Story Name_TC Name. For e.g., 3414_Swiggy mobile app_Check Landing screen.
Here, the User story refers to the requirement document. User Story ID is taken from bug tracking tools. For e.g., Jira, TDP, and Rally are some popular bug tracking tools.
2.3 Test Summary
Test Summary tells about summary of the test case. The test summary is written in one line. It should be precise and clear. The test summary should provide information about the whole test case.
2.4 Description
The description provides detailed information about the test case. It gives us the information about goal or purpose of the test case. The description can be more than one line.
2.5 Prerequisite or pre-condition
Prerequisites define the steps that should be followed before executing the test case. For e.g., For testing the landing screen, the prerequisite will be used should be logged in.
2.6 Test Data
Test data is the data required for executing the data.
2.7 Test Steps
Test steps have detailed instructions for running the test case. This is the most crucial section of a test case. In the test steps field, the tester should try for clear and unambiguous stages so that another person can follow the test steps during execution.
2.8 Actual Result
This field is only filled during the execution of the test. We write the actual result noticed during the test case execution in this area. The actual result indicates the outcomes obtained after test execution.
2.9 Expected Result
The expected result indicates the desired outcome in order to pass the test case.
We arrive at the intended outcome based on the test procedures performed and the test data utilized, such as the user should successfully log in and browse to the home page.
2.10 Test Case Status (Pass/ Fail)
Test case result is updated either pass/ fail depending upon the actual result and expected result. A test case status can be blocked except pass/ fail if requirements have not been delivered for testing.
2.11 Executed By
It shows the name of the tester or tester ID who has executed the test case.
2.12 Date
It shows the execution date. It keeps track of the execution date of various iterations during multiple sprints.
2.13 Comments
Comments give additional information added by the tester about test case execution. The tester may attach the link to the bug raised for that test case or requirement which helps team/ client to provide better picture of the bug.
We’d be pleased to answer any questions you have about test case or related to testing and how it may benefit your business.
TestDel is a leading quality assurance company with over 5 years of experience in providing all testing-related services to ensure the successful delivery of programmes. Our principal focus is to provide end-to-end quality assurance services around the world to Software Development firms and end clients. Our test teams work with organizations across all industries to meet all testing challenges effectively.
We are experts in manual and automated testing for web, desktop, mobile, cloud, and cross-platform software solutions. We’re here to make sure platforms are tested thoroughly on time and within budget to improve how the software works for the people who use it. You can trust our team of experienced and highly qualified professionals from reputed technology and management institutions who are domain experts from various industries including IT, Telecom Retail, Aviation, Utility, and Banking. Please Contact Us for more information.