Principle of Software Testing

1. Testing shows the presence of defects:-    
2. Exhaustive testing is impossible
3. Early testing
4. Defect clustering
5. Pesticide Paradox
6. Testing is context depending
7. Absence of error fallacy

1) Testing shows the presence of defects:-  

 Every application has some hidden defects that can not be identified by developers or clients itself that's why testing is mandatory to find the bug and develop a bugless system.

The testing's main objective is to identify bugs so that we can provide quality assurance to end-users for application.

Testing always provides that bug can be present on an application, the testing process never supports the absence of bug.

No one application in the IT industry that is 100% Bug-free.

2) Exhaustive testing is impossible:-  

if we test the application using multiple invalid data and valid data both to find a bug on the system that is called exhaustive testing.

If we want to test the large range of data then we never check complete data combination then we can consider some range-based data or specific data to test the application.

3) Early testing:-

This principle provides testing operation that should be done in the early stage of application development because if we do testing in the early-stage then we can easily identify the bug and create bug less system in less time and resources.

4) Defect clustering:-

 It is used to identify the most affected areas of an application that provide bug, in some cases, one small module creates multiple bugs into the system that thing is analyzed by defect clustering.

We should provide high priority to that module which raises 80% bug of an application to other modules and they itself cover 20% part of an application.

5) Pesticide Paradox:-

We should never satisfy our mind setup that an application is 100% defect-free because the application can show a defect anytime.

We should always restest, analyze all test cases to check the application bugs. we should review test cases regularly.

6) Testing is context depending:-

You should never use your imagination and thoughts to match the expected result and the actual result, it should be present as a context on SRS that will be managed to declare defects.

Every software system process will be different to implement testing because it depends on the context or relevant document to implement a testing operation.

7)Absence of error fallacy:-

It is not mandatory that software is 99% bugfree then it will succeed in the market because the main thing is software business needs should be matched by the client's requirement.

If software, not match business needs then this software never will be stable in the market