Proven Test Cases Creation for Beginners as Tester
As manual tester, the crucial part was to create a test case. However, while I was still studying this was not introduce to us but it was part of the process nowadays.
For today we will tackle about the list below:
- What is a test case?
- Why do we need to write a test case?
- Formats for a test cases
WHAT IS A TEST CASE
According to wikipedia “a test case is a specification of inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective.“
However, based on my own experience, a test case is a step by step execution of possible actions of the users using a certain application that should also meet the criteria of the said application.
WHY DO WE NEED TO WRITE A TEST CASE
As manual tester, writing a test case is the same importance as testing the app. It is important that you have these scenario in mind of what user will be executing based on the feature that you and your team are building. In addition, these test cases will be created in advance while the application is still in development.
When you are starting out, this might be hard to imagine but when you will be in this job longer, it will simple for you to create one. As long as you understand the requirements of the system.
FORMAT FOR A TEST CASE
There’s is no standard format for test cases. Only it got improved and transform overtime. You can actually create one as long it is simple and readable for everyone.
There are certain labels needed when you create a test case now. Below, are my own proven column headers of test cases.
| Column Name | Column Description |
|---|---|
| Test Case ID | A test case id. It should be relevant to the feature that you test. Ex. LGN001 |
| Env | Depends on what version or testing environment you are using. For mobile, it should be the version and what environment. For web, it should be what Jenkins job number of a certain environment it got deployed with. Ex. Mobile: Version 2.0.0 QA Env Web: Job#100 Dev Env |
| Module | Screen where this certain case will be performed. Ex. Login Screen |
| Summary | A short description of what is the certain test case is all about. Ex. Login with valid credentials |
| Test Data | Credentials of the said user or test data that will be use during the testing. Ex. URL: https://thisisyourwebsite.com/login Credentials: user@mail.com/123456 |
| Pre-condition | What is the things to set up in order for a certain case to work. Ex. User is not logged in. |
| Test Steps | The user step by steps instruction on how to operate a certain test case. Ex. 1. Launch the app 2. Input the URL in Test Data Column 3. Input credential in Test Data Column 4. Click Sign in |
| Expected Result | The expected output based on the requirements and user operations. Ex. 1. It should login the user 2. It should redirect user to dashboard screen |
| Actual Result | The actual output when a tester is executing the test case. If the result is the same as expected, input OK/PASSED. If not, then input FAILED, and create a bug ticket based on this test case and put it on Notes column. |
| Notes | Either it’s from the developer feedback or QA adding some feedback or bug tickets. |
| Date Tested | Date execution of the test cases. |
| Tested By | Who is the one will be testing the app. |
Basing with the above column header and examples, I hope it will help you out with creating your test cases. I’ve used this kind of format for many years and it is always effective. This kind of test cases is ready for automation.
