E

A B C D E F G

Emulator: A device that duplicates (provides an emulation of) the functions of one system using a different system, so that the second system behaves like (and appears to be) the first system. This focus on exact reproduction of external behavior is in contrast to simulation, which can concern an abstract model of the system being simulated, often considering internal state.

Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.

End-to-End Testing: Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, suing network communications, or interacting with other hardware, applications, or systems if appropriate.

Entry Point: The first executable statement within a component.

Equivalence Class: A mathematical concept, an equivalence class is a subset of given set induced by an equivalence relation on that given test. (If the given set is empty, then the equivalence relation is empty, and there are no equivalence classes; otherwise, the equivalence relation and its concomitant equivalence classes are all non-empty). Elements of an equivalence class are said to be equivalent, under the equivalence relation, to all the other elements of the same equivalence class.

Equivalence Partition: See Equivalence Class.

Equivalence Partitioning: Leverages the concept of "classes" of input conditions. A "class" of input could be "City Name" where testing one or several city names could be deemed equivalent to testing all city names. In other words each instance of a class in a test covers a large set of other possible tests.

Equivalence Partition Coverage: The percentage of equivalence classes generated for the component, which have been tested.

Equivalence Partition Testing: A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

Error: A mistake that produces an incorrect result.

Error Guessing: Error guessing involves making an itemized list of the errors expected to occur in a particular area of the system and then designing a set of test cases to check for these expected errors. Error guessing is more testing art than testing science but can very effective given a tester familiar with the history of the system.

Error Seeding: The process of injecting a known number of "dummy" defects into the program and then check how many of them are found by various inspections and testing. If, for example, 60% of them are found, the presumption is that 60% of other defects have been as well. See Debugging.

Evaluation Report: A document produced at the end of the test process summarizing all testing activities and results. It also contains an evaluation of the test process and lessons learned.

Executable Statement: A statement which, when complied, is translated into oobject code, which will be executed procedurally when the program is running and may perform an action or program data.

Exercised: A program element is exercised by a test case when the input value causes the execution of that element, such as a statement, branch, or other structural element.

Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test.

Exit Point: The last executable statement within a component.

Expected Outcome: See Predicted Outcome.

Expert System: A domain specific knowledge base combined with an inference engine that processes knowledge encoded in the knowledge base to respond to a user's request for advice.

Expertise: Specialized domain knowledge, skills, tricks, shortcuts and rules-of-thumb that provide an ability to rapidly and effectively solve problems in the problem domain.