Acceptance testing & UAT

The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.

A collaborative approach to development in which the team and customers are using the customers own domain language to understand their requirements, which …

Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance …

A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The …

A group of software development methodologies based on iterative incremental development, where requirements and solutions evolve through collaboration between …

Simulated or actual operational testing by potential users/customers or an independent test team at the developers' site, but outside the development …

A procedure determining whether a person or a process is, in fact, who or what it is declared to be.

Permission given to a user or process to access resources.

The response of a component or system to a set of input values and preconditions.

Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers, to determine whether or not a …

A logical expression that can be evaluated as True or False.

A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.

The degree to which a component or system can exchange information with other components or systems, and/or perform its required functions while sharing the …

The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.

Users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a software product is used.

Acceptance testing conducted to verify whether a system satisfies its contractual requirements.

A sequence of consecutive edges in a directed graph.

The protection of personally identifiable information or otherwise sensitive information from undesired disclosure.

A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the …

A human action that produces an incorrect result.

Testing based on the tester's experience, knowledge and intuition.

A test is deemed to fail if its actual result does not match its expected result.

The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified …

A result of an evaluation that identifies some important issue, problem, or opportunity.

A generally recognized rule of thumb that helps to achieve a goal.

The capability of the software product to enable the user to learn its application.

The number or category assigned to an attribute of an entity by making a measurement.

A measurement scale and the method used for measurement.

Testing based on or involving models.

The capability of the software product to enable the user to operate and control it.

Operational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff …

The consequence/outcome of the execution of a test.

Decision rules used to determine whether a test item has passed or failed.

Testing to determine the performance of a software product.

The ease with which the software product can be transferred from one hardware or software environment to another.

The level of (business) importance assigned to an item, e.g., defect.

The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.

Part of quality management focused on providing confidence that quality requirements will be fulfilled.

The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure.

Acceptance testing conducted to verify whether a system conforms to relevant laws, policies and regulations.

The capability of the software product to be used in place of another specified software product for the same purpose in the same environment.

The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the …

A factor that could result in future negative consequences.

A high-level document describing the principles, approach and major objectives of the organization regarding security.

A quality risk related to security.

An entity in a programming language, which is typically the smallest indivisible unit of execution.

Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., …

A set of one or more test cases.

The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking.

The activity that makes test assets available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to …

The process of running a test on the component or system under test, producing actual result(s).

A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are …

The component or system to be tested.

A distinct set of test activities collected into a manageable phase of a project, e.g., the execution activities of a test level.

The activity of establishing or updating a test plan.

A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post …

Documentation summarizing test activities and results.

The criteria used to guide the generation of test cases or to select test cases in order to limit the size of a test.

A skilled professional who is involved in the testing of a component or system.

The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and …

Acceptance testing carried out by future users in a (simulated) operational environment focusing on user requirements and needs.

A person's perceptions and responses resulting from the use or anticipated use of a software product.

All components of a system that provide information and controls for the user to accomplish specific tasks with the system.

A high-level user or business requirement commonly used in Agile software development, typically consisting of one sentence in the everyday or business language …

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.