Glossary of Software Testing Terms:
This glossary of software testing
terms and conditions is a compilation of knowledge, gathered
over time, from many different sources. It is provided as-is
in good faith, without any warranty as to the accuracy or
currency of any definition or other information contained
herein. If you have any questions or queries about the contents
of this glossary, please contact
Project Realms directly.
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
End-to-End Testing consists of testing the system from the defined
beginning point to the defined ending point to ensure all pieces
and integration points are working properly. (Tip to toe) Its
testing a complete application environment in a situation that
mimics real-world, use, such as interacting with a database,
using network communications, or interacting with other hardware,
applications, or system if appropriate.
End User Role
This testing role, usually played by one or more business area
associates, is responsible for consulting with other test team
members during the test effort on items such as requirements
definition and acceptance criteria. End users may have exclusive
responsibility for performing User Acceptance Testing or work
in partnership with the Business Technology area on that testing
Checks for memory leaks or other problems that may occur with
The first executable statement within a component.
A mathematical concept, an equivalence class is a subset of
a given set induced by an equivalence relation on that given
set. (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 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.
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.
A mistake that produces an incorrect result.
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 case to check for these expected errors.
Error guessing is more testing art than testing science but
can be very effective given a tester familiar with the history
of the system.
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 found as well. See Bebugging.
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.
Also referred to as: Findings Report, Test
A statement which, when compiled, is translated into object
code, which will be executed procedurally when the program is
running and may perform an action on program data.
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.
Testing which covers all combinations of input values and preconditions
for an element of the software under test.
The last executable statement within a component.
A domain specific knowledge base combined with a inference engine
that processes knowledge encoded in the knowledge base to respond
to a user's request for advice.
Specialized domain knowledge, skills, tricks, shortcuts and
rules-of-thumb that provide an ability to rapidly and effectively
solve problems in the problem domain.
Exploratory testing is the tactical pursuit of software faults
and defects driven by challenging assumptions. It is an approach
in software testing with simultaneous learning, test design
and test execution. While the software is being tested, the
tester learns things that together with experience and creativity
generates new good tests to run.
| Contact us for more info