Our 'Types of Software Testing' articles
Assessing risks that can cause a system to fail is essential. In this post, we discuss Risk-Based Testing, a technique for mitigating risk.
Configuration testing is how we find out which are the best hardware and software combinations so applications can work without any defects.
Happy path testing is usually the first test done on a new build, and shows testers how it should perform properly, so they can then test more thoroughly.
Which types of manual testing are the best? They all have different roles, so our post will help you to choose the right ones to use for your next project.
Adhoc testing is a type of unstructured testing meant to find defects and performance issues not found in more traditional approaches to testing.
What is beta testing? This post explains how beta testing is used for discovering a product’s overlooked flaws and glitches in a real-world environment.
Service oriented architecture testing assesses the software architecture (SOA) used for building business application using third-party services.
UAT and Beta Testing involve end-users providing feedback to the product team. They are often done just before the public release of a software product.
API Testing to checking that an intermediate layer in a software system that is responsible for data communication between the data source and the Graphical User Interface works correctly.
Grey box testing is a blend of both white box testing and black box testing. This type of testing is best for feature complete applications.