1.2. Example Test Case

Field Sample Entry Test TC_Login_01

Every test case is assigned a unique identifier known as the Test Case ID. This ID is crucial for tracking purposes, allowing testers and developers to reference specific tests quickly without confusion. For instance, the Test Case ID 'TC_Login_01' indicates it is the first test case specifically designed for testing the login functionality.

Think of the Test Case ID like a library book number. Just as every book has a unique ID to help you find it on the shelf, each test case has a unique identifier to help the team locate it in the documentation.

Test Verify login with valid credentials

The Test Objective clearly states what the test case aims to verify. In this case, the objective is to check if the login feature works correctly when the user provides valid credentials. This step ensures that the test is focused and allows testers to understand what to expect while executing the test.

Consider the test objective as the purpose of a recipe. Just like a recipe outlines what the dish should taste like, the test objective describes what the test aims to achieve.

Precond User is registered and on the login page

Preconditions are setup requirements that must be met before executing a test. For the login test case, it specifies that the user must already be registered and must navigate to the login page. This ensures that the test accurately reflects a real-world scenario.

Think of preconditions as the necessary steps to prepare for a game. Before playing, players need to be on the field and have the right equipment. Only then can the game be played fairly.

Test 1. Enter username 2. Enter password 3. Click Login

The Test Steps outline the specific actions that need to be taken to execute the test. In this example, the steps detail entering the username, submitting the password, and finally clicking the login button. Clearly defined steps help ensure that anyone executing the test can follow them accurately.

Imagine these steps as instructions for building a model. Just as you follow each step of an instruction manual to assemble the model correctly, testers follow these steps to verify the software functions as intended.

Expecte User is redirected to the dashboard Actual User redirected to dashboard

The Expected Result describes what should happen after executing the test steps, while the Actual Result states what happened in reality. Comparing these two results determines the success of the test case. In this situation, the test expects the user to be redirected to a dashboard after a successful login.

This is akin to planning a trip. The expected result is reaching your destination on time, while the actual result might be arriving late due to traffic. By comparing both, you understand what went wrong.

Status Pass Remark N/A

The Status indicates whether the test passed or failed, providing quick insight into the test's outcome. In this case, the test case passed, meaning the login functionality works as intended. Additional remarks can include any notable observations, but here it records 'N/A' indicating none are needed.

You can think of test status as grading a test. If a student answers all questions correctly, they pass; otherwise, they fail. The remarks would include any comments that clarify why they received that grade.

--