Test Cases in Software Testing Life Cycle (STLC)
- Test Cases means mostly how to test the software.
- A test cases is a document, which has a set of test data, preconditions, expected results etc, against a specific requirements or scenarios.
- The test cases is an in-details document that includes all possible inputs such as positive and negative, and the navigation steps. These are implemented during the testing process to check whether the software application is fulfilling all the requirements or not.
- The test case is defined as a group of conditions under which a tester determines whether a software application is working as per the customer's requirements or not.
- Test cases can be used in the future at the time of regression testing, sanity testing.
![]() |
What Is Test Cases And Test Scenarios In Software Testing Life Cycle (STLC)? |
How your test case be like or which kind of test case is good test case?
- Test case should cover all functionality.
- Test case should be understandable.
- Test case should be simple and easy.
We can write test cases in two ways:
- In JIRA
- Excel sheet
Test case template
The primary purpose of writing a test case is to achieve the quality and complete functionality of the application.
Test case contains below sections-
- Header
- Body
![]() |
Test Cases Header and Body |
![]() |
Test Cases Header |
![]() |
Test Cases Body |
As we know, the actual result is written after the test case execution, and most of the time, it would be same as the expected result.
But if the test case will fail, then we mark the status as Fail and then log a bug.We can comment bug id in the remark column.
Template can be different for some company but, for testing one application, all the test engineers should follow a usual template, which is 99% is like same.
The test case should be written in simple language so that a new test engineer can also understand and execute the same.
In the above sample template, the header contains the following:
TC number or Step number
It is also essential because if step number 20 is failing, we can document the bug report and hence prioritize the bug.
Release
One release can contain many versions of the release.This can be get from developer.
Pre-condition
These are the necessary conditions that need to be satisfied by every test engineer before starting the test execution process. Or it is the data that needs to be created for the testing.
Example-build url or username or password needed.
Test data
These are the values or the input we need to create as per the per-condition.
For example, Username-admin, Password-admin1234 and account number-xyz of the users.
The test lead may be given the test data like username or password to test the application, or the test engineer may themself generate the username and password.
Test Scenarios in Software Testing Life Cycle (STLC)
- Test Scenarios is mostly what to test.
- It covers end to end functionality of a software application in liner statements.
- The test scenario is a high-level classification of testable requirements.
- If we have requirements and desired output then how to achieve it, we have different ways, those ways are called scenarios.
- Suppose we have to purchase AC from flipkart or amazon.
- Then we have some ways for payment-
Product (AC) à Credit Card à Purchase (Way1)
Product (AC) à Debit Card à Purchase (Way2)
Product (AC) à Internet Banking à Purchase (Way3)
Now, Requirement is for payment and product purchase.
Scenario are Way 1, way 2 and way 3
Checking all these functionality in detail (positive and negative cases) is test case.
In test scenarios mostly positive condition taken care and in test case positive and negative both taken care.
![]() |
Test Scenarios In Software Testing Life Cycle (STLC) |
Difference Between Test cases and Test Scenarios
![]() |
Difference Between Test cases and Test Scenarios |
Read More Articles: What Is Smoke Testing, Sanity Testing and Regression Testing ?
No comments:
Post a Comment