1 . Box Testing specifically assessments the functionality of the software and doesn’t pay heed to internal design. software
2. White Box Testing checks the various internal software and codings that the software is built on. Code coverage is the key factor.
3. Unit Tests deals with the checking of the modules that the software is broken into and detailed knowledge of coding, hence usually done by the programmers.
4. Incremental Integration Testing tests the application constantly to ensure that the various added functions works perfectly.
5. The use Testing checks the quests when they are built-in with one another and inheritor dependency.
6. Functional Screening deals with the output that the software provides due to specific inputs provided.
7. System Testing provides test results for the whole system at a go rather than exploring the various modules. It provides an all over the result for the whole software system.
eight. End-To-End Testing shows how the software made will work in an environment which is same as the real world.
on the lookout for. Sanity Testing tests the application for its stability. That pushes the software to the extreme limits to show how it would work under pressure.
12. Regression Testing is one of the major types of software testing which covers the whole software and shows you the various alterations which the modules need for the program to be bug free.
11. Acceptance Testing checks if the software is up to the mark with the needs of the customer or the end user who will in turn decide the popularity of the software.
doze. Load Testing checks how the software will react under pressure or extreme load. Various levels of load are added to the system to check the response time under the condition and the functionality is thus checked.
13. Stress Testing sets excessive stress on the software, even beyond the specified limits, and inspections the productivity of the software under the on top of that stressed environment.
14. Performance Testing will check the performance ability of the system under various real world conditions that the software may face once launched in the market.
15. Usability Testing checks the ease with which a new user will be able to adapt to the software, the user friendliness of the interface and the smoothness of the circulation.
16. Install/Uninstall Testing bank checks the ease of set up of the program and the various upgrades that is to be available over time for the program as well as enough time taken for uninstalling the same.
17. Recovery Tests checks the time used for the software to heal up from probable crashes, failures of hardware and other magnamous problems that it could face once launched for public use.
18. Security Tests checks the ease or difficulty that the hackers will face to penetrate the particular software.
nineteen. Compatibility Testing deals with the way the software will react in the occurrence of various other software, the hardware of the system and the various operating systems it is going to run on.
20. Comparison Testing tests the application to its previous version to be able to see how much better or weak it has become after the modifications.
21. Alpha Testing is done in the house by building a virtual or fake environment consisting of end users to check the real world experience.
22. Beta Testing is the final testing done by the real world users who will use the software in future too.