When getting started with any type of QA testing, it’s always helpful to have test cases. But what are QA test cases, and why are they important? Read on to learn how they work, and how to write test cases.
What Should A Test Case Contain?
Well written test cases should contain the following aspects:
- Title or ID (ie: “LOG-1”)
- An association with a section of the site/app (ie: “Login”)
- Notes on any setup needed (for example, “access to a staging build” or “admin credentials”)
- Steps to follow to perform the test
- Expected results
Why Are Test Cases Important?
Having a suite of test cases makes the whole Agile QA process more efficient. It can also show new colleagues how the app or site is supposed to work — right down to even the smallest details.
Most importantly, having test cases that all team members can review ensures two crucial details:
- There are no gaps in test coverage. Let’s say that QA hasn’t been informed about a particular feature or requirement. By reviewing test cases, other team members can immediately determine if there’s missing test coverage.
- Everyone is on the same page. Sometimes there are misunderstandings about how a feature is supposed to work. When a developer or product manager looks at QA’s test cases, any misconceptions can be identified quickly. Continue reading →