Actual state
Refers to the behaviour of a software application or component as it is recorded during a test. Frequently, this actual state does not conform to the specifications on the software.
When the actual state is not as expected or required, work is undertaken to attain the target state.
Acceptance testing
Acceptance testing is performed on software by the customer following delivery. The aim of acceptance testing is to help the customer who commissioned the software to decide if all the requirements of the software have been fully implemented and to see whether to accept the software or not.
See also the acceptance testing part of the software testing article.
Alpha testing
This is testing by future customers and users - or independent teams of testers - in a simulated environment or environment that has been specially designed for testing.
Alpha testing can be understood as "internal acceptance testing".
Analyzer
This is a tool used to check formalised testing objects (e.g. source code for software applications) for certain attributes and quality hallmarks.
Analytical quality assurance
This describes diagnostic measures (e.g. testing) employed with the aim of checking the quality of a product.
Cf: quality asssurance.
Anomaly
Any deviation from the requirements formulated at the design stage, from documentation or standards based on clients'/users' experience.
Anomalies may be discovered through testing, analysis, reviews or through use of the software.
Audit
This is the independent evaluation of software carried out by an external organisation checking conformity to guidelines, standards, specifications and procedures that have been developed based on objective criteria.
Documents relating to the form, functions and contents of the product to be produced are also audited, along with written process for production and the specifications showing conformity with standards and guidelines or make conformity measurable.
Cf. audit in Wikipedia.