Let’s get started with the Test Case Tutorial
Now that you have an understanding of what a test case is, it’s time to start practicing writing your test cases. In this section of the test case tutorial, we will walk you through how to write excellent test cases, provide an example test case, and recommend tools for writing and organizing your test cases.
Writing test cases requires having access to existing information or documentation about the software. It’s not uncommon for testers to write test cases based on information provided in user stories. In this part of the test case tutorial, you’ll learn how to transform a user story into a test case.
Testing involves more than ensuring the software does what it’s supposed to do. It’s equally important to verify the software doesn’t do certain things and to understand at what point does the software break? In this section of the test case tutorial, we look at the three main types of test cases: positive, negative, and destructive.
Test cases can build up over time. As software requirements change, or parts of the application get deprecated, this results in many test cases becoming obsolete. Just like it’s important to groom a backlog, it’s essential to maintain your library of test cases. This part of the test case tutorial provides tips and best practices for keeping your test cases up to date, clean, and organized.
Jake Bartlett lives and works in San Francisco, and has a background in software testing, customer support, and project management.
Brian is a QA Engineer with over 15 years of broad experience to draw on as a regular blog contributor for TestLodge.