Software Testing Axioms

Overview

Let’s learn about Software Testing axioms in this tutorial. As a software tester, it is essential to be aware of the “fundamental truths” of the field when testing software products. These statements are established through consistent practice and the extensive experience of many testers.

Software Testing Axioms

Software Testing axioms are fundamental truths or principles that are universally accepted in the field of software testing. Some of the software testing axioms are as follows:

• Software Testing shows the presence of defects
• Exhaustive Testing is Impossible
• Software testing is risk-based.
• The more bugs you find, the more bugs there are.
• Not all bugs found will be fixed.
• Product Specifications are not final
• Software Testing is context-dependent

Software Testing shows the presence of defects.

While software testing can reveal the presence of defects, it cannot guarantee the absence of defects in the software product. Although it does reduce the likelihood of undiscovered defects remaining in the software, not finding any defects through testing does not necessarily prove the software’s correctness.

Exhaustive Testing is Impossible

Testing every combination of inputs, states, paths, and interactions in a software system is impossible. Testing should focus on areas of higher risk and impact. There is always more to test, scenarios to cover, risks to assess, and feedback to collect.

Software testing is risk-based

Risk-based testing is an approach to software testing that prioritizes the tests of features and functions of the software application based on the risk of failure, the impact of failure, and the likelihood of failure. This approach is based on the premise that we can never test everything, so we must prioritize our testing efforts based on risk.

Not all bugs found will be fixed.

Not all defects or bugs identified during software testing or after release will be fixed. There are various reasons and factors for this axiom.

Fixing a defect requires resources such as developer time, testing, and possibly new infrastructure. If the cost to fix a defect outweighs the benefit, it may not be fixed.

Introducing changes to software products can sometimes result in new defects or affect other parts of the software. If fixing a bug could potentially lead to more significant issues, it may be left unresolved.

Product specifications are not final.

Product specifications may change during software development due to factors such as customer needs, market conditions, technology updates, budget changes, and stakeholder feedback.

Software Testing is context-dependent.

Testing strategies, techniques, and tools should be tailored to the specific context and needs of each software product, domain, user, and environment since software testing is context-dependent and there is no one-size-fits-all approach to testing.

These axioms help guide the testing process and are essential for understanding the essence and purpose of software testing.