• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off

Card Range To Study



Play button


Play button




Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

31 Cards in this Set

  • Front
  • Back
Defect (bug, fault)
A flaw in a component or system that can cause the component or system to fail to
perform its required function, e.g. an incorrect statement or data definition. A defect, if
encountered during execution, may cause a failure of the component or system.
Error (mistake)
A human action that produces an incorrect result.
Deviation of the component or system from its expected delivery, service or result.
The degree to which a component, system or process meets specified requirements
and/or user/customer needs and expectations. [After IEEE 610]
A factor that could result in future negative consequences; usually expressed as impact
and likelihood.
Computer programs, procedures, and possibly associated documentation and data
pertaining to the operation of a computer system. [IEEE 610]
The process consisting of all lifecycle activities, both static and dynamic, concerned
with planning, preparation and evaluation of software products and related work products
to determine that they satisfy specified requirements, to demonstrate that they are fit for
purpose and to detect defects.
Artifacts produced during the test process required to plan, design, and execute
tests, such as documentation, scripts, inputs, expected results, set-up and clear-up
procedures, files, databases, environment, and any additional software or utilities used in
Exhaustive (complete) testing
A test approach in which the test suite comprises all combinations of
input values and preconditions
Testing that runs test cases that failed the last time they were run, in order to
verify the success of corrective actions
Regression testing
Testing of a previously tested program following modification to ensure
that defects have not been introduced or uncovered in unchanged areas of the software, as a
result of the changes made. It is performed when the software or its environment is
The process of finding, analyzing and removing the causes of failures in
A condition or capability needed by a user to solve a problem or achieve an
objective that must be met or possessed by a system or system component to satisfy a
contract, standard, specification, or other formally imposed document. [After IEEE 610]
An evaluation of a product or project status to ascertain discrepancies from planned
results and to recommend improvements.
Test basis
All documents from which the requirements of a component or system can be
inferred. The documentation on which the test cases are based.
Test case
A set of input values, execution preconditions, expected results and execution
postconditions, developed for a particular objective or test condition
Confirmation testing
is a synonim of re-testing
Exit criteria
The set of generic and specific conditions, agreed upon with the stakeholders,
for permitting a process to be officially completed.
Entry criteria
The set of generic and specific conditions for permitting a process to go
forward with a defined task, e.g. test phase.
Any event occurring that requires investigation
Test condition
An item or event of a component or system that could be verified by one or
more test cases
Test coverage (coverage)
The degree, expressed as a percentage, to which a specified coverage item has been
exercised by a test suite.
Test data
Data that exists (for example, in a database) before a test is executed, and that
affects or is affected by the component or system under test.
Test execution
The process of running a test on the component or system under test,
producing actual result(s).
Test log
A chronological record of relevant details about the execution of tests.
Test plan
A document describing the scope, approach, resources and schedule of intended
test activities. It identifies amongst others test items, the features to be tested, the testing
tasks, who will do each task, degree of tester independence, the test environment, the test
design techniques and entry and exit criteria to be used
Test strategy
A high-level description of the test levels to be performed and the testing within
those levels for an organization or programme (one or more projects).
Test policy
A high level document describing the principles, approach and major objectives
of the organization regarding testing.
Test summary report
A document summarizing testing activities and results. It also contains
an evaluation of the corresponding test items against exit criteria.
Test control
A test management task that deals with developing and applying a set of
corrective actions to get a test project on track when monitoring shows a deviation from
what was planned.
The capability of the software product to enable modified software to be tested.
[ISO 9126]