extreme programming (XP)

A software engineering methodology used within agile software development whereby core practices are programming in pairs, doing extensive code review, unit testing of all code, and simplicity and clarity in code. See also agile software development.

exploratory testing

An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests. [After Bach]

experience-based testing

Testing based on the tester’s experience, knowledge and intuition.

experience-based test design technique

Procedure to derive and/or select test cases based on the tester’s experience, knowledge and intuition.

experience-based technique

See experience-based test design technique.

expected result

The behavior predicted by the specification, or another source, of the component or system under specified conditions.

expected outcome

See expected result.

exit point

An executable statement or process step which defines a point at which a given process is intended to cease..

exit criteria

The set of generic and specific conditions, agreed upon with the stakeholders for permitting a process to be officially completed. The purpose of exit criteria is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing. [After Gilb and Graham]

exhaustive testing

A test approach in which the test suite comprises all combinations of input values and preconditions.

exercised

A program element is said to be exercised by a test case when the input value causes the execution of that element, such as a statement, decision, or other structural element.

executable statement

A statement which, when compiled, is translated into object code, and which will be executed procedurally when the program is running and may perform an action on d .

exception handling

Behavior of a component or system in response to erroneous input, from either a human user or from another component or system, or to an internal failure.

evaluation

See testing.

establishing (IDEAL)

The phase within the IDEAL model where the specifics of how an organization will reach its destination are planned. The establishing phase consists of the activities set priorities, develop approach and plan actions. See also IDEAL .

error tolerance

The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].

error seeding tool

See fault seeding tool.

error seeding

See fault seeding.

error guessing

A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them.

error

A human action that produces an incorrect result. [After IEEE 610]