A test case is a set of clear steps and conditions designed to check if part of a system behaves in the way we expect. It typically includes the starting point, the actions to take, and the outcome we expect to occur.
For example, imagine you are testing an online shop. A test case could be “Successfully log in with valid credentials.” The test case would include the URL of the login screen. The valid credentials, steps to take and what to expect when successfully logged in, e.g. an indicator or specific screen.
Test cases can be written down in detail or kept as lightweight notes, depending on the context and risk. They give you a repeatable way to explore the system, confirm expected results, find bugs, and share your understanding with others. They are also a way of making thinking visible, helping teams see what has been tested and where gaps might exist. Test Cases are normally considered more formal than other formats, such as user stories, as they tend to detail all steps required for execution.
For example, imagine you are testing an online shop. A test case could be “Successfully log in with valid credentials.” The test case would include the URL of the login screen. The valid credentials, steps to take and what to expect when successfully logged in, e.g. an indicator or specific screen.
Test cases can be written down in detail or kept as lightweight notes, depending on the context and risk. They give you a repeatable way to explore the system, confirm expected results, find bugs, and share your understanding with others. They are also a way of making thinking visible, helping teams see what has been tested and where gaps might exist. Test Cases are normally considered more formal than other formats, such as user stories, as they tend to detail all steps required for execution.
