Information Technology Reference
In-Depth Information
Ad hoc testing:
Testing carried out informally; no formal test preparation takes
place, no recognized test design technique is used, there are no expectations for
results, and arbitrariness guides the test execution activity.
Adaptability:
The capability of the software product to be adapted for differ-
ent specified environments without applying actions or means other than those
provided for this purpose for the software considered. [ISO 9126] See also
portability
.
Agile testing:
Testing practice for a project using agile methodologies, such as
extreme programming (XP), treating development as the customer of testing, and
emphasizing the test-first design paradigm. See also
test-driven development
.
Algorithm test:
See
branch testing
.
Alpha testing:
Simulated or actual operational testing by potential users/customers
or an independent test team at the developers' site, but outside the development
organization. Alpha testing is often employed for off-the-shelf software as a form of
internal acceptance testing.
Analyzability:
The capability of the software product to be diagnosed for deficien-
cies or causes of failures in the software, or for the parts to be modified to be identi-
fied. [ISO 9126] See also
maintainability
.
Analyzer:
See
static analyzer
.
Anomaly:
Any condition that deviates from expectation based on requirements
specifications, design documents, user documents, standards, and so on, or from
someone's perception or experience. Anomalies may be found during, but not lim-
ited to, reviewing, testing, analysis, compilation, or use of software products or
applicable documentation. [IEEE 1044] See also
defect, deviation, error, fault, fail-
ure, incident,
or
problem
.
Arc testing:
See
branch testing
.
Attractiveness:
The capability of the software product to be attractive to the user.
[ISO 9126] See also
usability
.
Audit:
An independent evaluation of software products or processes to ascertain
compliance to standards, guidelines, specifications, and/or procedures based on
objective criteria, including documents that specify the following:
1. The form or content of the products to be produced
2. The process by which the products shall be produced
3. How compliance to standards or guidelines shall be measured. [IEEE 1028]
Audit trail:
A path by which the original input to a process (e.g., data) can be
traced back through the process, taking the process output as a starting point. This
facilitates defect analysis and allows a process audit to be carried out.
Automated testware:
Testware used in automated testing, such as tool scripts.
Availability:
The degree to which a component or system is operational and acces-
sible when required for use. Often expressed as a percentage. [IEEE 610]
