Identify defects · S/W Testing

Principles of Software Testing

1.Testing shows the presents of defects

Its can shows the defects of presents, but can’t prove these are no defects even after testing the application or product, therefore we can’t say that the product is  either 100%  defect or not

Its always reduces the no of “undiscovered” defects remaining in the s/w, but even if no defects are found, its not a proof of correctness

2. Exhaustive testing is impossible

Testing everything including all combination of inputs and the condition is not possible so instead of doing the exhaustive testing we can use “risk and priories” to focus testing efforts so accessing and managing risk is one of the most important activities and reason for testing in any project

3.Early Testing

In the SDLC, Testing activities should starts as early as possible and should be focused on define “Objective”

4. Test results shout be inspected regularly (meticulously)

5. When the test objective is to defect the defect, the “good” test case is one then has the high probability of reveling a yet “undefeated defect”

6. A test case was contain the expected output or result

7. Test cases should be developed for both valid / invalid input

8. Defect Clustering

A small no of modules contains most of the defects, deserved, during release testing or show the most operational failures.

9. Pesticide paradocx

If the same kinds of test are repeated again and again, eventually the same set of test case will know longer be able to find any “new bugs” to over come this pesticide paradocxis really very important to review the test case regularly and new and different test case need to be written to  exercise different parts of software / system to potentially found out the “more defects”

10. The probability of exerts of  additional defects the software component is propositional to the no of defect already defected to that component additional defects propositional to  no of defects already detected”

11. Testing should carried out by  a group that is independent of the development groups

12. Testing should be repeatable and reusable

13. Testing should be planned

14. Testing activities should be inter operable into the s/w life cycle

15. Its a creative challenging task

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s