Software testing Principles

 It is important that you achieve optimum test results while conducting software testing without deviating from the goal, but the way you determine which you are following the proper approach for testing? For that, you want to stick to a few primary trying out principles. here are the commonplace seven testing standards which can be widely practiced within the software enterprise.

To understand this, don't forget a scenario where you're moving a record from folder A to Folder B.

think about all the viable approaches you can take a look at this.

apart from the standard scenarios, you could additionally test the following situations

• looking to pass the document when it's far Open

• You do not have the security rights to stick the file in Folder B

• Folder B is on a shared power and garage capability is full.

• Folder B already has a file with the same name, in reality, the list is countless

• Or think you've got 15 enter fields to check, each having five feasible values, the variety of combos to be tested could be 5^15

 

Below are the 7 Principles:

1)   1. Testing shows presence of defects:

Testing can shows only defects are present or not in current application, But 100% defect free software is impossible.

2)   2. Exhaustive testing is not possible:

If we test a functionality with all possible inputs called Exhaustive testing, But it require huge resources, So exhaustive testing is not possible.

3)   3. Defect Clustering:

Sometimes, small modules will produce more no of defects than bigger functionality at the time, we should conduct more testing on that type of risky module called defect clustering.

4)   4. Pesticide paradox:

If we are not able to finding defects with existing test cases then add some more test cases or modify existing test cases called pesticide paradox for better testing.

5)   5. Early Testing:

As soon as possible, conducting testing in SDLC process(SDLC life cycle) which is called early testing.

6)   6. Testing is context dependent:

Testing is basically requirement dependent. So, different kinds of sites are tested differently.

7)   7. Absence of Errors Fallacy:

Testing can shows only defects are present or not in current application, But 100% defect free software is impossible.