_edited_edited.png)
In this blog, we will learn about How to write test cases. Now I explain the summary of how to write a manual test case, it would be: 1. Identify the feature or functionality to test. 2. Create a list of test cases that define specific actions to validate the functionality. Let’s see the detailed steps for writing test cases.
Step 1 – Test Case ID:
In this step, the tester will assign a unique identifier to the test case. This allows the tester to recall and identify the test case in the future easily.
Example: TC-01: Verify Login Functionality for a User
Step 2 – Test Case Description:
The tester will describe the test case, outlining what it is designed to do. The tester may also provide a brief overview of the expected behavior. An Example: Test Case Description: Test for Logging Into the application Given: A valid username and password for the web application When: User enters the username and password in the login page Then: the user should be able to log in to the application successfully. The Home page for the application should be displayed.
Step 3 – Pre-Conditions:
The tester will document any pre-conditions that need to be in place for the test case to run properly. It may include initial configuration settings or manually executing some previous tests. A Pre-Condition example in testing could be that the test environment must be set up, to be very similar to the production environment, including the same hardware, operating system, and software.
Step 4 – Test Steps:
The tester will document the detailed steps necessary to execute the test case. This includes deciding which actions should be taken to perform the test and possible data inputs.
Example steps for our login test:
1. Launch the login application under test.
2. Enter a valid username and password in the appropriate fields.
3. Click the ‘Login’ button.
4. Verify that the user has been successfully logged in.
5. Log out and check if the user is logged out of the system.
Step 5 – Test Data:
The tester will define any necessary test data. For example, if the test case needs to test that login fails for incorrect credentials, then test data would be a set of incorrect usernames/passwords.
Step 6 – Expected Result:
The tester will provide the expected result of the test. This is the result the tester is looking to verify. Examples of how to define expected results:
1. A user should be able to enter a valid username and password and click the login button.
2. The application should authenticate the user’s credentials and grant access to the application.
3. The invalid user should not be able to enter the valid username and password; click the login button.
4. The application should reject the user’s credentials and display an appropriate error message.
Step 7 – Post Condition:
The tester will provide any cleanup that needs to be done after running the test case. This includes reverting settings or cleaning up files created during the test case. Example: 1. The user can successfully log in after providing valid credentials. 2. After providing invalid credentials, the user is shown the appropriate error message. 3. The user’s credentials are securely stored for future logins. 4. The user is taken to the correct page after successful login. 5. The user cannot access the page without logging in. 6. No unauthorized access to the user’s data.
Step 8 – Actual Result:
The tester will document the actual result of the test. This is the result the tester observed when running the test. Example: After entering the correct username and password, the user is successfully logged in and is presented with the welcome page.
Step 9 – Status:
The tester will report the status of the test. If the expected and actual results match, the test is said to have passed. If they do not match, the test is said to have failed.
Example: Tested the valid login functionality. Result: The user can log in with valid credentials. Overall Test Result: All the test steps were successfully executed, and the expected results were achieved. The login application is functioning as expected. Tested for Invalid Login functionality. Result: The user is unable to log in with invalid credentials. Overall Test Result: The invalid login functionality has been tested and verified to be working as expected.
Comments