Software Testing

                                           Software Testing

      

           Traditionally, Testing is defined as been narrowly confined to testing the program code. There are many reasons which clearly show us why Software Testing is important. Almost everything, we use today has an element of software in it. Today in a typical workplace and at home, just about everyone uses a Computer and Software. Everyone is an organization and at home uses E-mails and the Internet for communication, education, entertainment, interaction and for getting any information they want. Also, the technical people use programming languages, modeling tools, and database management systems for the task that they were mostly executing manually a few years earlier.

           The above examples are just for some instances where the use of the software is obvious to the users. First, an organization that develops any form of S/W product or service must put in every effort to highly reduce and eliminate any defects in each delivered product and services. Second, defects are unlikely to remain hidden for long. When the no of users was limited and the way they use the product was also predictable, it was quite possible that there could be defects in S/W product they would never get defected or uncovered for a very long time. Third, the nature of the usage of the product or service is becoming increasingly unpredictable.

Software Testing

        

 Fundamental principles of Testing:-

1. The goal of testing is to find defects before customers find them out.
2. Exhaustive testing is not possible, program testing can only show the presence of defects, never their absence.
3. Test the test first.
4. Understand the reason behind the test.
5. The test developed immunity and have to be revised constantly.
6. Defects occur in clusters(memory chunk), and testing should focus on these clusters.
7. Testing encompasses defect prevention.
8. Intelligent and well-planed automation is key to realizing the benefits of testing.

       Testing isn't meet to replace other ways of ensuring quality. It is one of the methods to detect the defect in an S/W. The idea of the catching defect within each phase, without letting them reach the testing phases, lead us to define two more terms i.e. Verification and Validation. Verification is the process of evaluating a system or component to determine whether the product of a given phase satisfy the conditions imposed at the start of that phase. Verification takes care of  the activities to focus on the question"Are we building the product right?"  

       Validation is the process of evaluating a system or component during or at the end of the development process to determine it satisfies specific requirements. Validation takes care of a set of activities to address the question "Are we building the right product?".

     

There are so many testing, the names are given bellow-

• WhiteBox Testing
• BlackBox Testing
• Positive and Negative Testing
• Integration Testing
• Functional and Non-Functional Testing
• Beta Testing
• Stress Testing
• Interoperability Testing
• Acceptance Testing
• Performance Testing
• Regression Testing