Types of Testing Flashcards
Understand types of testing
Integration Testing
Testing the interaction between different modules or services within an application to ensure they work together properly
System Testing
Testing the entire system as a whole to ensure that it meets the specific requirements
Acceptance Testing
Determine whether the software is ready for delivery. Ensures the system meets the business requirements and is often done by end-users or clients
Sanity Testing
A quick test performed after receiving a new build to check if the critical functionalities work as expected without major issues
Smoke Testing
A preliminary test to check if the basic functions of an application are working before moving forward with more detailed testing
Exploratory Testing
Unscripted testing where testers explore the application to discover defects or improvements without predefined test cases
Ad-hoc Testing
Informal testing conducted without a structured approach, aiming to find defects that might have been missed by other types of testing
Regression Testing
Re-testing of previously tested functionality after changes (bug fixes or new features) to ensure the updates haven’t introduces new issues
Usability Testing
Evaluates how user-friendly and intuitive the software is from an end-users perspective
Compatibility Testing
Ensure that the software works on different devices, browsers, operating systems, and environments
Localization and Internalization Testing
Focuses on adapting the software to different languages, regions, or cultures by verifying content, layout, and functionality. E.g. Can display different languages without breaking the layout or functionality, strings and characters are correctly supported, and region formatting (dates, time, numbers, currencies)
Unit Testing
Testing individual units or components of the software to ensure they function properly. E.g. testing functions from the code
API Testing
Checks the interactions between different software systems via Application Programming Interfaces (APIs). This includes validation of request-response and data formats
Database Testing
Verifies that database operations like data storage, retrieval, and integrity are working as expected. E.g. CRUD
UAT Testing
Performed by end users or stakeholders to validate that the system meets business requirements and is ready for release.
Interface Testing
Tests the interfaces between different modules or systems, ensuring data exchange happens correctly and reliably
E.g. Unit testing, integration testing, API testing, GUI testing, security testing, load testing, performance testing, regression testing, system testing, and acceptance testing
Security Testing
Checks for vulnerabilities in the software, ensuring that the system is protected against threats like unauthorized access, data breaches, and attacks.
Stress Testing
Pushes the system beyond its normal operational capacity to test its breaking point and observe how it recovers from failure.
Load Testing
Checks the system’s behavior under a specific expected load to ensure it can handle a certain number of concurrent users or transactions.
Performance Testing
Measures how the system performs under various conditions. It includes testing the speed, scalability, and stability of the software.
Scalability Testing
Evaluates the software’s ability to scale up or down, in terms of users, data, or resources, without compromising performance.
Reliability Testing
Ensures that the system can function consistently under expected conditions over time, without failure.
Compliance Testing
Ensures the system meets certain regulations, standards, or laws, such as GDPR for data privacy or industry-specific standards.
Maintainability Testing
Evaluates how easy it is to modify, update, or fix the system. It ensures the software can be maintained with minimal effort.
Boundary Testing
Tests the boundaries or edges of input domains. Identify defects at the limits of input values where errors are more likely to occur.
- The smallest (minimum) and largest (maximum) values of an input range.
- Values just inside (valid) and just outside (invalid) the boundaries.
State Transition Testing
Verifies behavior when the system transitions between different states based on events or inputs.
