27 Types of Testing in 2 minutes

One line definition different types of testing

1. Acceptance testing is done check the workflow of the system and to make sure business requirements are working and reproducible for user interaction.
2. Alpha testing is done to test the product before it is released into the market.
3. Automation testing uses scripts to test the product.
4. Backward compatibility testing is done to ensure the new implemented features do not conflict with the existing features.
5. Beta testing is done by customers to check the product in real time.
6. Black box testing is done to check the requirement of system and its functionality without knowing the implemented internal mechanism.
7. Boundary value testing is used to test the boundaries of patrician to find defects. like effects of a<1 when it should be of a≤1.
8. Comparability testing is done to check if the product works in various infrastructure like different OS, hardware, etc.
9. Continuous testing is a type of automated testing where a product is tested continuously and results are accumulated to get more accurate result.
10. Data integrity testing is used to check the validity of the data after operation is performed on it.
11. End to end testing checks the product in a real world environment.
12. Functional testing is a black box testing which validates that for a given input the output behaves in an expected way.
13. Integration testing checks if the two different components work in harmony with each other.
14. Interface testing checks weather the two components in the system works in harmony with each other.
15. Load testing is a non-functional test used to find the maximum number of workload a system can handle without degradation to performance.
16. Manual testing is a hands on approach where a group of individuals test the product.
17. Monkey testing is done by giving random sequence of input to the given application without caring about the workflow or type of input.
18. Penetration testing is used to simulate cyber attacks to find and exploit the weakness in a system.
19. Performance testing is used to check if the product fulfills the performance requirement.
20. Recovery testing is used to check if the system recovers after crash.
    Regression testing is used to verify the previously working features in last version is working in current version.
21. Sanity testing is done to check if the product is stable for major testing.
22. Smoke testing is done by the QA team for a new developers release to verify that there are no major or critical issues.
23. Stress testing is running a workload on system belong its capability and increasing quantity till the system fails.
24. UI testing is done to see the how the application handles user input from external peripherals like mouse, keyboard, touch scree.
25. Unit testing is done by developers to verify if the part of code (functions) of a components delivers the desired output.
26. Usability testing checks the user friendliness of an application.
27. White box teasing is done by developers who know the internal mechanism of the code to test the logic used by the code.