Quality assurance in software involves many different approaches to testing. It’s nearly impossible to test everything, but you can certainly get close by narrowing in on the different types of test cases that do and ask specific things. To discover which type to use for which purpose, you need to consider all the different types of testing and filter the test cases best suited for helping you totesting that uses for its base achieve the highest quality product.
Some of these areas can overlap with others, but in general, each type of software testing and each category of test case has a specific purpose. In this post we’re going to look at some of the most common types of test cases in the world of software testing.
Different types of test cases:
Functionality Test Cases
Functionality test cases are used to discover if an application’s interface works with the rest of the system and its users. The tests identify the success or failure of functions that the software is expected to perform.
The cases are a type of black-box testing that uses for its base, the specifications or user stories of the software under test. This allows the tests to be performed without needing access to the workings or internal structures of the software being tested. The QA team are usually the writers of functionality test cases because the task falls within normal QA processes. They can be written and run as soon as development makes a first function available for testing. To help steer development, they can be written in advance of the code, if all the tester has access to are the requirements.
As specified above, they can be written and run as soon as it is viable to do so and they should be repeated whenever updates are added, right through to when customers become a possibility.
Example: Confirming a user can successfully upload a profile photo.
User Interface Test Cases
User interface test cases are used to verify that specific pieces of the Graphical User Interface (GUI) look and work as expected. These types of test cases can be used to identify cosmetic inconsistencies, grammar and spelling errors, links, and any other elements the user interacts with or sees.
These cases are usually written by the testing team but the design team may also be involved as they are most familiar with the interface. User interface test cases are the types of test cases in software testing that usually drive cross-browser testing. Browsers tend to render things differently, and user interface test cases help ensure your application behaves consistently across multiple browsers.
These test cases will be run once the development phase is complete and the UI is hooked up to the database.
Example: What happens when the website is viewed on a small screen such as a mobile phone? Does the UI break?
Performance Test Cases
Performance test cases validate response times and overall effectiveness of an application. That is, after executing an action, how long does it take for the system to respond? Performance test cases should have a very clear set of success criteria.
The testing team typically writes these test cases and they are often automated. A large application can have hundreds or thousands of performance tests. Automating these tests and running them frequently helps expose scenarios where the application is not performing at the expected level.
Performance test cases help with understanding how the application will perform in the real world. These cases can be written once the testing team has received performance requirements from the product team. However, many performance issues can be identified manually without having specified requirements.
Example: How long does it take for the system to authenticate a user, and load the next page? When multiple people login at the same time, does the application remain stable?
Integration Test Cases
Integration test cases are meant to determine how different modules interact with each other. The main purpose with integration test cases are to ensure interfaces between the different modules are working properly.
The testing team identifies which areas should undergo integration testing, while the development team will have input on how those test cases should be written. Either of these two teams may work to write the cases.
They verify that modules that are already working individually, are also able to work together.
Example: Checking the link between the home page and the “favorites” section. When you add an item as a “favorite”, from the homepage, does it appear in the “favorites” section?
Usability Test Cases
Usability test cases can often be referred to as “tasks” or “scenarios”. Rather than providing detailed step-by-step instructions to execute the test, the tester is presented with a high level scenario or task to complete.
Usability test cases help identify how a user naturally approaches and uses the application. They help guide the tester through various situations and flows. No prior knowledge of the application is necessary.
Example: Can the user successfully add more than one item to their shopping cart? How is that experience?
Database Test Cases
Test cases for database testing examine what’s happening behind the scenes. The user interface is clean, and everything appears to be working… but where is all that data going?
In order to write these test cases, you need to have a strong understanding of the entire application, the database tables, and the the stored procedures. The testing team will often use SQL queries to develop database test cases.
Database tests are used to verify the developer has written the code in a way that stores and handles data in a consistent, safe manner.
Example: Let’s consider the creation of a user profile. When the user submits their profile, the following should be tested in regards to the database.
- Did the application store the inputted data in the database?
- Was any data lost in the process?
- Partially performed data should not have been saved.
- Unauthorized users should not be able to view or access the user’s information.
Security Test Cases
Security test cases help ensure the application restricts actions and permissions wherever necessary. These test cases are written to protect data when and where it needs to be safeguarded.
Security test cases are used to drive penetration testing and other types of security-based tests.
Authentication and encryption are often the main focus in security test cases. The security team (if one exists) is usually responsible for writing and conducting these tests.
Example: If a user reaches X number of failed login attempts, does the account become locked? Is a user able to upload data without being logged in?
User Acceptance Test Cases
User acceptance test cases, or “UAT” test cases, help the team test the user acceptance testing environment. These test cases should be broad, covering all areas of the application.
The purpose of these test cases isn’t to find bugs (hopefully they’ve already been found and fixed in previous testing), but to verify the application is acceptable to the user. So, when they execute a test, are the results of that test, and the experience of that test acceptable?
Since many other types of testing have already been done by the time UAT starts, the focus is not so much on a granular level, but more so on the bigger picture. User acceptance test cases are used by the end-user or client and prepared by the testing team or product manager. This is perhaps the most important phase of testing as it is the last step before going into production.
Example: If testing for instance, a photo management application for a photography studio, the client (the user) should test that they are able to upload and manage their photos in a way that fits their business needs.
Test cases come in all different shapes and sizes. Depending on the type of test case being written, you may need a more technical background, or one in UX in order to effectively write a good test case.
Each type of software testing requires different types of test cases. By considering the above types of test cases when you design your tests, you’ll maximize test coverage and go into the release with more confidence.