[go: up one dir, main page]
Scribd
Upload
11 views1 page

Principles of Software Testing

Software testing aims to identify defects, but cannot guarantee a defect-free product. Exhaustive testing is impractical, and early testing can reduce costs associated with defect detection. Key principles include defect clustering, the necessity of context-dependent testing, and the importance of meeting user requirements beyond just minimizing bugs.

Uploaded by

afreen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
11 views1 page

Principles of Software Testing

Software testing aims to identify defects, but cannot guarantee a defect-free product. Exhaustive testing is impractical, and early testing can reduce costs associated with defect detection. Key principles include defect clustering, the necessity of context-dependent testing, and the importance of meeting user requirements beyond just minimizing bugs.

Uploaded by

afreen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Principles of Software testing - Software Testing

1. Testing shows the Presence of Defects


The goal of software testing is to make the software fail. Software testing reduces the
presence of defects. Software testing talks about the presence of defects and doesn't talk
about the absence of defects. Software testing can ensure that defects are present but it can
not prove that software is defect-free. Even multiple tests can never ensure that software is
100% bug-free. Testing can reduce the number of defects but not remove all defects.
2. Exhaustive Testing is not Possible
It is the process of testing the functionality of the software in all possible inputs (valid or
invalid) and pre-conditions is known as exhaustive testing. Exhaustive testing is impossible
means the software can never test at every test case. It can test only some test cases and
assume that the software is correct and it will produce the correct output in every test case.
If the software will test every test case then it will take more cost, effort, etc., which is
impractical.
3. Early Testing
To find the defect in the software, early test activity shall be started. The defect detected in
the early phases of SDLC will be very less expensive. For better performance of software,
software testing will start at the initial phase i.e. testing will perform at the requirement
analysis phase.
4. Defect Clustering
In a project, a small number of modules can contain most of the defects. The Pareto
Principle for software testing states that 80% of software defects come from 20% of
modules.
5. Pesticide Paradox
Repeating the same test cases, again and again, will not find new bugs. So it is necessary to
review the test cases and add or update test cases to find new bugs.
6. Testing is Context-Dependent
The testing approach depends on the context of the software developed. Different types of
software need to perform different types of testing. For example, The testing of the e-
commerce site is different from the testing of the Android application.
7. Absence of Errors Fallacy
If a built software is 99% bug-free but does not follow the user requirement then it is
unusable. It is not only necessary that software is 99% bug-free but it is also mandatory to
fulfill all the customer requirements.
Software testing is essential for ensuring applications meet user expectations and function
correctly. Understanding key principles like detecting defects early and recognizing the
impossibility of exhaustive testing is vital for delivering reliable software.

You might also like