Introduction
When I started learning software testing, I chose a To-Do List application for practice because it is simple and easy to understand. It also has basic features that are commonly used in many applications.
Application Features
A To-Do List application allows users to:
- Add a task
- Edit a task
- Delete a task
- Mark a task as completed
These features are enough to understand how testing works.
Test Case Format
To write test cases, I used a simple table format with columns like BRS, Test Case ID, Scenario, Steps, Test Data, Expected Result, Actual Result, and Result. This format helps to keep everything organized and clear.
Testcase:To-do list
Test Design Approach
While creating test cases, I focused on three main types:
- Positive testing: checking normal functionality like adding or deleting a task
- Negative testing: checking invalid inputs like empty task
- Edge cases: checking limits like long text or multiple tasks
Explanation of Test Cases
Each test case covers one function of the application. For example, adding a task checks whether the task is saved properly, and deleting a task checks whether it is removed from the list. Other cases like editing and marking tasks ensure that all features are working correctly.
Key Learning
From this, I learned that test cases should be simple and easy to understand. It is important to test both valid and invalid scenarios. Thinking from a user perspective also helps in writing better test cases.
