DEPARTMENT of
INFRASTRUCTURE,
ENERGY and RESOURCES
“Acceptance Testing”
The Acceptance Testing Kit
Glossary
for
Projects with an IT Enhancement
or Procurement Component
A Guide
for
Project and Acceptance Test Managers
Version B
August 2001
Information Management Branch
Corporate Services
The Acceptance Testing Kit – Glossary
Glossary of Terms
Acceptance Criteria
Generated by the system end-users and owners to determine if the final
outputs of the system are in line with what the Business Unit requires and
expects.
Acceptance Testing
Acceptance Testing is a process undertaken by end-users, operators and
maintainers of a system to test a system to ensure it meets business
requirements. It is sometimes called User Acceptance Testing (UAT).
Acceptance Test Environment
The hardware, software, and network environment within which a system
will be tested.
Acceptance Test Log
A log maintained throughout Acceptance Testing by the Acceptance Test
Manager and System Administrator to recording significant events and
changes to the Test environment and Test data.
Acceptance Test Plan
A structured document outlining the Acceptance Test approach, the
objectives, the activities, the responsibilities, and the detail schedule.
Change Management (1)
A formal process implemented to manage and minimise the impact of
change in an organisation.
Change Management (2)
A formal process to request a change to a controlled product. This may be a
system, a document (such as the System Business Specifications), a test
environment, a contract etc. The process includes assessment of the impact
and cost, and authorisation, prior to implementation.
Database Integrity
When data within a database retains internal consistency and lack of
corruption.
Database Integrity Checking Routines
Processes (programs or scripts) that check the overall integrity of a (test)
database. The routines scan the database tables and links and report any
logical data integrity problems such a missing relationships, undefined
codes, etc. They may also check the physical integrity of the database.
1
The Acceptance Testing Kit – Glossary
Database Script
A (database) program to written to undertake a specific database
administration task such as changing the structure of the database, checking
the database or taking a database backup copy.
End-user
Any individual who will be at the “receiving end” of the system from an
operational perspective. They may be inputting or extracting data, or simply
generating reports.
Expected Results
The expected outcome of a test.
Function Points
A measure of the size of a system, based on the Function Point Analysis
methodology and discipline. Function points count, categorise, and qualify
the business functions of the system. They are a technology-independent
method of estimating the amount of work associated with developing a
system.
GITC
Acronym for Government Information Technology Contract.
Operating Environment
The hardware, software and network environment in which the system will
run.
System Owner
This may be the Business Unit Manager, the Project Sponsor, or another key
stakeholder. They will usually have a vested interest in the outputs and
outcomes from the system.
Parallel Running
Where the existing system(s) continue to operate as normal, while the new
system duplicates all processes and activities. The results from the old and
new systems can be compared as a means of testing the new system. Parallel
running is normally conducted after implementation prior to a full
changeover to the new system. Parallel running may also occur as part of
Acceptance Testing.
2
The Acceptance Testing Kit – Glossary
Performance Test
Performance testing is where specific system functions (usually critical ones)
are timed under various system loads to ensure that the times meet
contractual performance criteria. System loads may include network traffic,
database activity as well as normal system functions.
Problem Reports
A formal record of an Acceptance Test problem that defines the problem, the
conditions under which it occurred, and the details of the software version in
use. It may also be used to record details of the resolution of the problem.
Problem Report Register
An index of all problem reports, summarising their status and relevant dates.
Regression Testing
Where a series of tests (or all tests) are repeated, where the expected results
are known. The expected results are based on the same tests that have been
successfully completed at an earlier time.
Roll-back Recovery
Where the database management software automatically undoes database
changes made by a transaction if the transaction fails to complete. The
transaction may fail because records it needs have changed or have become
locked, the database is not responding, or through program failure.
Roll-forward Recovery
When a database has become corrupt and unusable, the database is restored
from an earlier backup and the system transaction log (recorded since the
backup was taken) is applied to the restored database. This is intended to
bring the database to a status as near as possible to its most recent.
Sociability Testing
Testing of the impact of a new system on existing systems and the
operational environment to ensure the new system does not adversely affect
the existing environment and software.
Stakeholder
Any person or organisation that has an involvement with or responsibility
for a system or who is a beneficiary of the system.
3
The Acceptance Testing Kit – Glossary
Stress Testing
Where specific system functions (usually critical ones) are subjected to high
load to ensure that the system can cope with such loads. The functions to be
tested can be on-line or batch. Stress tests may also focus on a particular
aspect of the system’s architecture such a database updating to ensure for
example, that the database server’s capacity is adequate.
Test (1)
A single test, usually against one business requirement, showing the test to
be performed (with any specific data or conditions) and the expected
outcome. There may be many Tests for single business requirement.
Test (2) (generic definition)
A trial that determines a function’s fitness for purpose. A critical trial or
examination of one or more properties of an item.
Test Case
A single record or group of records used in a Test.
Test Condition
A circumstance that must exist or a state an item under test is expected to
have, to enable a particular Test to be undertaken.
Test Data Identifier
Test Procedure
Documentation of the steps that make up a formal process to be followed
during Acceptance Testing.
Test Result
The record of the outcome of each Test.
Test Result Register
An index of all Tests, summarising their overall results and relevant dates.
Test Scenario
A Test Script.
Test Script
A Test Script is a documented process involving a series of steps, many of
which will be a series of interrelated Tests. The Script may also describe a
series of Test Conditions.
4
The Acceptance Testing Kit – Glossary
Test Strategy
A document that outlines the overall Test approach and sets the rules and
understandings for testing activities during a Project. These may be included
in the Project Execution Plan.
Transaction Log
An (internal) log of all database changes made by a system. The log is
recorded automatically by the database management software.
User Acceptance Testing (UAT)
See Acceptance Testing.
Volume Testing
Verifies that the time required for entering, processing, and printing out
typical volumes of data meets end-user business requirements. An
additional aspect is to test processing times for large volumes of data.
(Similar to Performance and Stress Testing).
5