What is a test case?

How to write effective functional and regression tests
Get started Free Mini Regression Test
Digital Quality Has Evolved
More complexity and shorter cycles
As deployment windows shrink, many teams struggle to test as thoroughly and as frequently as they should.
As a result your digital assets begin to break in new and unexpected ways at the expense of your customer’s experience.
More Devices
Higher User Expectations
Faster Releases
Test Case #1
Test Case #2
Test Case #3
Better quality starts with better test cases
A test case is a set of steps required to accomplish a specific outcome.
Running test cases gives you confidence that important features are working as desired.
A suite of effective test cases lets you know your website or app is working correctly.
Anatomy Of A Test Case
Test Case Title
Give your test a clear and descriptive name.
Screen Size
What screen size should the testers use?
Other Requirements
Include any other details the tester will need (e.g. passwords, credentials, data sets, etc.)
Test Case
Test Location
Tell the tester where to access the feature.
Test Description
What do you want to test? This may be a list of individual items or a sequence of steps. Specify the expected result.
How long should my test case be?
We don’t limit the number of steps per test case, but we do recommend keeping them between five to ten steps.
If you find yourself with more than that, you should consider breaking it up into separate test cases.
Is your test case too long?

Cramming too many steps in a single test is not an effective way to test.

It inevitably creates bottlenecks in the testing process, makes it more difficult to interpret and remediate failures, and creates challenges when you begin to scale your test suite.
Six reasons to keep test cases short
It’s easier to isolate why the test failed.
It’s faster to run each individual test case.
Testers are less likely to misunderstand the test.
It’s easier to maintain and scale your test suite.
Complex test cases may indicate usability issues.
It’s quicker to replicate and remedy issues.
Test case examples
Adding a product to the cart
Adjusting product quantities
Creating a customer account
Applying a coupon code
Forgot customer account password
Checking out as a guest
Removing an item from the cart
Internal order notification
Customer received an order confirmation
Stock level adjusted
How to write better test cases
Use consistent naming conventions
Even though each test case should be standalone, a consistent structure and naming convention will make it easier to manage, execute and maintain your suite as you scale.
Focus on one thing
Each test case should focus on a single outcome. Unfocused test slow down testing, complicate remediation and undermine the scalability of your testing suite.
Write positive and negative test cases
Don’t assume your users will only use your site or app in the ways you intend. Create negative test cases that validate error messages and other failures.
Start with your ‘golden path’
Rather than tackling everything at once, consider how most users engage with your website or app. What devices do they use? How do they browse? Which features are most important?
Automate where possible
If you can easily and reliably automate a test, you should. Automation is a fast, scalable way to get confidence that your website or app is working as expected.
…But don’t try to automate everything
It’s difficult to automate some features, some organisations are moving so fast it doesn’t make sense to create automation scripts, and sometimes it’s simply too expensive.
Don’t get left in the dust
The most important part of testing is actually doing it! Comprehensive libraries of test cases are only valuable if they are consistently run and the fede

Continuous QA for your web apps

Functional & regression testing with experienced testers
Get started How it works