Welcome to the Manual Testing Free Training series.
In the last tutorial, we talked about the Test case and Test plan concepts. Please refer to the following to learn about the Test case and Test plan:
https://www.qaonlinetraining.com/test-case-test-plan-manual-testing-free-training/
All right!! Let’s move ahead. In this tutorial, we are going to talk about the following stuff:
1. Test case template.
2. Sample test case.
Before moving further, let’s take a brief look at the stages of the Test case:
Stage 1: In this stage, you write basic test cases from the available specification and user documentation.
Stage 2: Basically this is the practical stage in which you write test cases based on the functionality and system flow of the application.
Stage 3: In this stage, you will group all test cases and write a test suite. The test suite is nothing, but it is a group of test cases.
Stage 4: This is the automation stage of the project or application. In the automation stage, there is no interaction between humans and applications.
Now, we can talk about the Test case template:
In the template, we have 2 parts:
Information of test case:
- Project Name: Application module (what you are going to test)
- Created By: The name of the author of the test case.
- Date of Creation: Date of creation of test case.
- Testing Environment: The environment
Fields of Test case template.
These are the following fields that we need to add to the template:
- Test Suite ID: ID of test case suite (group of this test case) [if required]
- Test case ID: Test case ID is the unique identity of a test case.
- Test case Summary: It is the Summary / Objective of the Test case
- Prerequisites or preconditions: preconditions, must be fulfilled before the test case.
- Test steps: steps of the test case.
- Test data: test data are used to be while processing the test.
- Expected Result: The expected result of the Test
- Actual Result: Actual result generate after execution of test
- Status: Pass, fail after execution of the test. Other statuses are “Not Executed” if the test is not performed or “Blocked” if the test is blocked.
- Post conditions: Post Conditions, execute the steps successfully (if required)
- Remarks (if required)
For Instructor-led training
https://www.qaonlinetraining.com/programs/master-of-manual-testing
For Self-Driven training
https://www.itlearn360.com/self-paced-courses/qa-manual-tester-beginner-to-advance/
Sample test case
Project Name | Code Traverse Registration and Login Module | ||||||||
Created By | Infotek Solutions Inc. | ||||||||
Creation Date | 14th May 2022 | ||||||||
Testing Environment | OS: Windows 7 Ultimate
Browser: Google Chrome |
||||||||
Test case ID | Test case Summary | Preconditions | Steps | Test data | Expected Result | ActualResult | Post Condition | Status | |
Testcase01 | Test registration module of www.codetraverse.com | Register page should be available |
|
|
User has registered successfully | User has registered successfully | Email should be sent to New registered user | Pass |
That’s how we create the test case. If you’d like to download the test case template, please refer to the following link:
https://d33fi7o7l87at9.cloudfront.net/uploads/2022/05/TestCaseTemplate.xlsx
Conclusion
In this article, we talked about the test case template and created a sample test case. To check other stuff in this series, please refer to the following link:
https://www.qaonlinetraining.com/category/manual-testing/
→ The upcoming article in this Master of Manual testing training series will be about – How to test an e-commerce website.
Happy learning, until then!