Principles of Software Testing

The following are the principles of software Testing:

1) Bug detection:

Software testing aids in the detection of bugs. Although software testing minimizes the likelihood of undiscovered problems remaining in the software, it is not a guarantee of correctness.

2) Effectiveness Testing:

It will be unlikely or impossible to review and test all possible sets of beta modules and scenarios unless the project is under test and has a simple structure with minimal input.

3) Early Testing:

The sooner you begin testing your project or software, the better you will be bale to make use of your available time. Fixing a Defect early in the testing process is substantially less expensive.

4) Clustering defect:

During testing, you will see that the bulk of the defects or issues identified are due to a small number of software modules. Approximately 80% of the issues are identifies in about 20% of the modules.

5) Testing is context-dependent:

Context-dependent refers to the phenomena of how much easier it is to retrieve information when the "context", or conditions surrounding the memory, are the same for both encoding and retrieval. The software that has been produced is not all the same. Depending on the application, you might utilize different procedures, techniques, and types of testing.

For example, testing a retail POS system differs from testing an ATM machine.

6) Error-free software is a myth:

There is no such error thing as error-free software. When developing software, there are bound to be problems or errors, and you must test it thoroughly before releasing it. Finding and correcting flaws won't assist if the system is unusable and doesn't meet the user's demands and requirements.

7) Pesticide Paradox:

Repeating the same test cases will not result in the discovery of new bugs. To detect new bugs, it is required to evaluate the test cases and add or update test cases.