1. Box Testing explicitly tests the usefulness of the product and doesn’t pay regard to inner plan.
2. White Box Testing checks the different inward programming and coding that the product is based on. Code inclusion is the primary factor.
3. Unit Testing manages the checking of the modules that the product is broken into and requires nitty gritty learning of coding, subsequently generally done by the software engineers.
4. Gradual Integration Testing tests the application ceaselessly to ensure that the different included capacities works impeccably.
5. Reconciliation Testing checks the modules when they are incorporated with one another and beneficiary reliance.
6. Useful Testing manages the yield that the product gives because of explicit sources of info gave.
7. Framework Testing gives test results to the entire framework at a go as opposed to checking the different modules. It gives an everywhere throughout the outcome for the whole programming framework.
8. Start to finish Testing demonstrates how the product you have created will work in a situation which is same as this present reality.
9. Mental stability Testing tests the product for its security. It stretches the product to as far as possible to demonstrate how it would function under strain.
10. Relapse Testing is one of the significant kinds of programming testing which covers the whole programming and demonstrates to you the different alterations which the modules requirement 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 thusly choose the notoriety of the product.
12. Burden Testing checks how the product will respond under strain or unreasonable burden. Different measures of burden are added to the framework to check the reaction time under the condition and the usefulness is in this way checked.
13. Stress Testing puts over the top weight on the product, even past as far as possible, and checks the profitability of the product under the moreover focused on condition.
14. Execution Testing will check the execution capacity of the framework under different genuine conditions that the product may confront once propelled in the market.
15. Ease of use Testing checks the simplicity with which another client will almost certainly adjust to the product, the ease of use of the interface and the smoothness of the stream.
