Various Types of Software Testing



  1. Parallel Testing : Parallel Testing is mainly used for understanding and come to a conclusion of how much strength does our software has or weakness software has. This can be explained in such a way were the company wants to migrate from the existing application to  new application. This testing is done to ensure that both the existing(old) and newly developed application are working similarly.
  2. Reliability Testing: This testing is done to validate whether the software which we have prepared takes the abnormal state to normal state. This is known as “Recovery testing”.
  3. Intersystem Testing: This testing is done to check whether our software is adaptable with other software to share common resources.
  4. Load Testing : Load Testing can be defined as measurement of customer expected performance (processing) is called as Load Testing. Another name for Load testing is Scalability Testing.
  5. Endurance Testing : Testing the software build continuously to estimate durability of the software is called as Endurance Testing
  6. Stress Testing : Testing of customer expected load to estimate peak load is called as Stress Testing.
  7. Installation Testing : Testing the software by installing the software into customer side is called as Installation Testing.
  8. User interface Testing : Testing the user interface by checking the Graphical user interface of the software product.
  9. Manual Support Testing : Manual support testing can be explained as help document, testing is done to check  whether the manual which we have written is working as specified or not. Anyone who is new to the application can read this manual document and understand how it basically works.
  10. Configuration Testing : Configuration Testing is done to validate whether our software build is supporting the different technologies.
  11. Data volume Testing : The Data volume testing is done to validate how much does our software build is able to withstand the user related data. When Data volume testing is done we will be able to identify the response time and how system behaves when large volume of data is imposed on Database.
  12. Compatability Testing : compatability Testing is done to check whether our software build is able to work in different Operating Systems, networks, mobiles, tablets etc..
  13. Regression Testing : Regression testing is done to validate whether the new bug fixes does not impact the existing functionality.
  14. Retesting : Retesting can be defined as testing the software after the bug fixed by the developer and closing the defect after the retest.


Please enter your comment!
Please enter your name here