axioms

Taxomony for the Test Axioms website.

acceptance
(3)

The process by which stakeholders determine whether a system (or intermediate product) is acceptable with respect to their goals and concerns (product risks).

axioms
(2)

An axiom is something believed to be true, but cannot be proven in any practical way.

confidence
(2)
coverage item
(1)

An entity or item derived from our test model that we wish to exercise in our tests.

defect
(2)

A manifestation of human error in our system. Defects can cause systems to fail in serious and often unpredictable ways.

Synonyms: fault, bug
environment
(1)

All systems need to be tested in context. What this means is that for a test to be meaningful, the system to be tested must be installed, set up, deployed or built in a realistic environment that simulates the real world in which the system will be used.A test environment is the technical context in which a test is executed. A realistic environment replicates all of the business, technical and organisational context.

event
(1)
evidence
(6)

Every test should have value to stakeholders. The tests that we run have value to stakeholders in that they provide evidence to support their acceptance decision making.

exit criteria
(4)

A set of targets to be met by a test stage to plan when to stop testing.

Synonyms: exit criteria, closure criteria, completion criteria
good-enough
(2)
incident
(1)
outcome
(1)

A test outcome is the outcome of a test, when executed. The outcome provides evidence that the system under test meets (or does not meet) are requirement, for example.

product
(0)

Products represent the intermediate and final deliverables of a project.

Synonyms: deliverable
product risk
(0)

Represent the ways in which intermediate products or the final system could fail or be defective. They relate to the definition of the system, the stability (or lack) of requirements, the complexity of the system, and the defect-proneness of technology which could lead to failures.

project intelligence
(1)

The information, data, and analysed outcomes (the evidence) from testing. (Project intelligence is analogous to battlefield intelligence in a military campaign).

re-test
(1)

A test that when last run – caused a failure and is re-run to demonstrate that defect fixes have been implemented correctly.

Synonyms: confirmation test
regression test
(1)

A test that when last run – passed and is re-run to demonstrate that defect fixes have not caused unwanted side-effects.

repeat-test
(1)
sources of knowledge
(0)

The documents, people, systems or experiences that support their test basis, test oracle and coverage models.

stakeholder
(3)

A tester’s stakeholders are those people who have an interest in the outcome of tests, and the information that testers provide.

stakeholder goal
(0)

The overall goals that the system to be tested, when implemented, is intended to achieve

test
(1)
test axioms
(1)

A set of context-neutral rules for testing that identify the critical thinking processes and motivations for all test approaches.

test basis
(2)

The source or sources of knowledge on which the test model and test oracle are derived.

test coverage
(2)

Describes how we assess the thoroughness or completeness of our testing with respect to our test model.

test design
(7)

The process of selecting things to test from a test model.

test oracle
(1)

The source of knowledge against which the behaviour of the system under test (test outcome(s)) will be compared.

unplanned event
(0)

Events that can have an adverse effect on our ability to conduct tests, cause delay, undermine our testing or represent failures of the system under test to behave as predicted by our oracle.

Synonyms: observation, anomaly, problem