1. Box Testing explicitly tests the usefulness of the product and doesn’t pay notice to inner plan.
2. White Box Testing checks the different inner programming and codings that the product is based on. Code inclusion is the fundamental component.
3. Unit Testing manages the checking of the modules that the product is broken into and requires itemized information on coding, thus generally done by the software engineers.
4. Gradual Integration Testing tests the application consistently to ensure that the different added capacities works impeccably.
5. Joining Testing checks the modules when they are incorporated with one another and beneficiary reliance.
6. Practical Testing manages the result that the product gives because of explicit information sources gave.
7. Framework Testing gives test results to the entire framework at a go as opposed to actually looking at the different modules. It gives an all around the outcome for the whole programming framework.
8. Start to finish Testing shows how the product you have created will work in a climate which is same as this present reality.
9. Mental soundness Testing tests the product for its dependability. It stretches the product to the outrageous edge to show how it would function under tension.
10. Relapse Testing is one of the significant kinds of programming testing which covers the whole programming and shows you the different alterations which the modules need for the product to be without bug.
11. Acknowledgment Testing checks whether the product is sufficient with the necessities of the client or the end client who will thus choose the ubiquity of the product.
12. Load Testing checks how the product will respond under tension or inordinate burden. Different measures of burden are added to the framework to check the reaction time under the condition and the usefulness is subsequently checked.
13. Stress Testing puts unnecessary weight on the product, even past as far as possible, and actually looks at the efficiency of the product under the also focused on climate.
14. Execution Testing will check the exhibition capacity of the framework under different genuine conditions that the product might confront once dispatched on the lookout.
15. Ease of use Testing checks the simplicity with which another client will actually want to adjust to the product, the ease of use of the interface and the perfection of the stream.
16. Introduce/Uninstall Testing checks the simplicity of establishment of the product and the different updates that will be accessible over the long haul for the product just as the time taken for uninstalling the equivalent.
17. Recuperation Testing checks the time taken for the product to mend up from likely crashes, disappointments of equipment and other magnamous issues that it could confront once dispatched for public use.
18. Security Testing checks the straightforwardness or trouble that the programmers will face to infiltrate the specific programming.
19. Similarity Testing manages the manner in which the product will respond within the sight of different other programming, the equipment of the framework and the different working frameworks that it will run on.
20. Examination Testing tests the product to its past adaptation in order to perceive how much more grounded or feeble it has become later the alterations.
21. Alpha Testing is done in the house by establishing a virtual or phony climate comprising of end clients to actually take a look at this present reality experience.
22. Beta Testing is the last testing done by this present reality clients who will utilize the product in future as well.
