Welcome to the Test Axioms website. This site hosts the current and all future definitions of the axioms.

Paul Gerrard introduced the idea of Test Axioms in posts on his blog in the spring of 2008. Over a few months their definitions evolved and in May 2008 he summarised the thinking behind them and tabulated 16 proposed axioms. Further evolution has occurred and with some changes, they have been used in the Tester’s Pocketbook.

There was quite a reaction to the proposed axioms. Some people rejected the idea, saying there were no such things. Others were more supportive and offered new axioms or alternate definitions.

Paul believes that there are a set of rules or principles that provide a framework for all testing. But there is no single agreed definition of test. This is mostly because every consultant and author has tended to write their own definition to suit their own purposes (and Paul admits to being as guilty as the rest of them). As an industry, we are hamstrung because of this. Our clients are confused, and we get distracted by discussions on definitions because of not-invented-here mentalities and our competitive instincts.

An axiom is something believed to be true, but cannot be proven in any practical way. It could be disproven by experiment or experience and we should be prepared to be proven wrong and welcome attempts to do this.

But some people object to the notion of Test Axioms and say that nothing in testing is certain. There are no axioms. All testing rules, principles, techniques, approaches etc. are heuristic. Heuristics have value in some contexts, but are limited in application, usefulness, accuracy etc. in other contexts. They are limited or fallible in known ways.

Here is a different way of looking at axioms then. The axioms have been defined in a way that testers can, for all practical purposes, regard them as axiomatic. If anyone devises a testing context where the axioms are violated, we need to think again: Perhaps the axiom should be scrapped or changed or its scope of applicability defined.

So far, Paul has not received any concrete examples that invalidate the Test Axioms as stated in the Pocketbook.

The Test Axioms are an attempt to provide a context-neutral set of rules for testing that identify the critical thinking processes and motivations for all test approaches.

The axiom definitions have been extracted from the book The Tester’s Pocketbook. If you want a hardcopy of the axioms and further background on their derivation and how to use them, we suggest you buy a copy!

Definitions

The Tester's Pocketbook proposes a set of Test Axioms that provide a framework for all testing. But there is no single agreed definition of test. This is mostly because every consultant and author has tended to write their own definition to suit their own purposes (and I am as guilty as the rest of them)....

Read more ...

Test, Testing

The word test is used as a noun and as a verb. We need a definition of test that is context-neutral and the most suitable definition comes from the American Heritage Dictionary. Test: (noun) a procedure for critical evaluation; a means of determining the presence, quality, or truth of something; a trial This statement seems...

Read more ...

Context-Neutral

In the preface of The Tester's Pocketbook Paul says:

Read more ...

Stakeholder Obsessed

Testing is an information or intelligence-gathering activity performed on behalf of (people who I will call) testing stakeholders. The manager who asked you to test could be your most important stakeholder (ask them!) They think testing is important enough to get someone as important as you involved – but might not be able to articulate...

Read more ...

Tester’s Pocketbook

All of the material relating to Test Axioms on this website has been extracted from the Tester's Pocketbook. The Pocketbook provides the background to the axioms as well as guidelines for using them in defining test approaches and strategies as well as conducting testing assessment and improvement activities. In a Pocketbook format, it's a handy...

Read more ...

Paul Gerrard

Paul Gerrard is a consultant, teacher, author, webmaster, programmer, tester, conference speaker, rowing coach and publisher. He has conducted consulting assignments in all aspects of software testing and quality assurance, specialising in test assurance. He has presented keynote talks and tutorials at testing conferences across Europe, the USA, Australia, South Africa and occasionally won awards...

Read more ...