|Software Testing Glossary Series|CTFL|A|


ACCEPTANCE CRITERIA:
Acceptance Criteria is the criteria where a system or deliverable component must satisfy the client requirements and well accepted by user, customer or any other authorized entity.

ACCEPTANCE TESTING:
Acceptance Testing is the testing which carries formally in order to meet the client’s needs, requirements, and business processes. This testing is conducted to verify whether or not a system satisfies the acceptance criteria and to determine whether or not to accept the system.

ACCESSIBILITY:
The degree to which a component or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use.

ACCESSIBILITY TESTING:
Accessibility Testing is to ascertain the repose by which users with disabilities can use a component or system.

ACTUAL RESULT:
Actual Result is the result/behavior which system/component produced while testing.

AD-HOC REVIEWING:
A review technique carried out by independent reviewers informally, without a structured process.

ALPHA TESTING:
ALPHA TESTING is the simulated or actual operational testing conducted in the developer's test environment, by roles outside the development organization.

ANOMALY:
Anomaly is the condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc., or from someone's perception or experience. Anomalies may be found during-but not limited to-reviewing, testing, analysis, compilation, or use of software products or applicable documentation.

AUDIT:
Audit is an independent scrutiny of a work product, process, or set of procedure that is performed by a third party to assess compliance with specifications, standards, contractual agreements, or other criteria.

AVAILABILITY:
The degree to which a component or system is operational and accessible when required for use.

References: Glossary definitions on ISTQB website.
                    Wikipedia  

No comments:

Post a Comment

|Software Testing Glossary Series|CTFL|N|O|P|

Non-Functional Requirement: Non-Functional Requirement is a requirement that describes how the component or system will do what it is s...