Terms related to Foundation Extension - Acceptance Testing 2019

Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
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 keywords are interpreted by special supporting scripts that are called by the control script for the test.
A group of software development methodologies based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.
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.
A logical expression that can be evaluated as True or False.
Acronym for Computer Aided Software Engineering.
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 same hardware or software environment.
The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.
A logical expression that can be evaluated as True or False.
The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.
Users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a software product is used.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
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 table. Data-driven testing is often used to support the application of test execution tools such as capture/playback tools.
A human action that produces an incorrect result.
A procedure to derive and/or select test cases based on the tester's experience, knowledge and intuition.
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 interface.
A distinguishing characteristic of a component or system.
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.
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 keywords are interpreted by special supporting scripts that are called by the control script for the test.
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.
A human action that produces an incorrect result.
Testing based on or involving models.
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 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 focusing on operational aspects, e.g., recoverability, resource-behavior, installability and technical compliance.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
Decision rules used to determine whether a test item has passed or failed.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
The degree to which a component or system uses time, resources and capacity when accomplishing its designated functions.
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.
An unknown underlying cause of one or more incidents.
A set of interrelated activities, which transform inputs into outputs.
Operational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on operational aspects, e.g., recoverability, resource-behavior, installability and technical compliance.
A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources.
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.
A category of product attributes that bears on quality.
The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure.
The capability of the software product to be used in place of another specified software product for the same purpose in the same environment.
A tool that supports the recording of requirements, requirements attributes (e.g., priority, knowledge responsible) and annotation, and facilitates traceability through layers of requirements and requirements change management. Some requirements management tools also provide facilities for static analysis, such as consistency checking and violations to pre-defined requirements rules.
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 program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions.
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.
Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.
A distinguishing characteristic of a component or system.
An entity in a programming language, which is typically the smallest indivisible unit of execution.
Documentation that provides a detailed description of a component or system for the purpose of developing and testing it.
Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., ISO/IEC standards, IEEE standards, and organizational standards).
An entity in a programming language, which is typically the smallest indivisible unit of execution.
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 program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions.
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 relevant stakeholders.
The process of running a test on the component or system under test, producing actual result(s).
The component or system to be tested.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
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 execution.
Documentation summarizing test activities and results.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
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 execution.
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 procedure used to derive and/or select test cases.
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 related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an actor can be a user or anything that can exchange information with the system.
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 capturing what functionality a user needs and the reason behind this, any non-functional criteria, and also includes acceptance criteria.
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.