Term
|
Definition
| Testing performed by submitting commands to the software under test using programming interfaces of the application directly. |
|
|
Term
|
Definition
| Testing performed by submitting commands to the software under test using a dedicated command-line interface. |
|
|
Term
|
Definition
| Testing performed by interacting with the software under test via the graphical user interface. |
|
|
Term
|
Definition
|
|
Term
|
Definition
| The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking. |
|
|
Term
| test automation architecture |
|
Definition
| An instantiation of the generic test automation architecture to define the architecture of a test automation solution, i.e., its layers, components, services and interfaces. |
|
|
Term
|
Definition
A person who is responsible for the design, implementation and maintenance of a test automation architecture as well as the technical evolution of the resulting test
automation solution. |
|
|
Term
| test automation framework |
|
Definition
| A tool that provides an environment for test automation. It usually includes a test harness and test libraries. |
|
|
Term
|
Definition
| A high-level plan to achieve long-term objectives of test automation under given boundary conditions. |
|
|
Term
|
Definition
Ref: After Fewster and Graham
Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures,
files, databases, environment, and any additional software or utilities used in testing.
|
|
|
Term
|
Definition
| Commonly used to refer to a test procedure specification, especially an automated one. |
|
|
Term
|
Definition
Ref: After TMap
Synonyms: test driver
A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.
|
|
|
Term
|
Definition
| The level to which a test object is modified by adjusting it for testability. |
|
|
Term
|
Definition
Ref: After IEEE 610
A skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It replaces a called
component. |
|
|
Term
|
Definition
| A customized software interface that enables automated testing of a test object. |
|
|
Term
|
Definition
| A person who is responsible for the planning and supervision of the development and evolution of a test automation solution. |
|
|
Term
|
Definition
Synonyms: capture/replay, record/playback
A test automation approach, where inputs to the test object are recorded during manual testing in order to generate automated test scripts that could be executed later (i.e.
replayed).
|
|
|
Term
|
Definition
Ref: Fewster and Graham
See Also: keyword-driven testing
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.
|
|
|
Term
| generic test automation architecture |
|
Definition
| Representation of the layers, components, and interfaces of a test automation architecture, allowing for a structured and modular approach to implement test automation. |
|
|
Term
|
Definition
See Also: data-driven testing
Synonyms: action word-driven testing
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.
|
|
|
Term
|
Definition
| A simple scripting technique without any control structure in the test scripts. |
|
|
Term
| model-based testing (MBT) |
|
Definition
| Testing based on or involving models. |
|
|
Term
|
Definition
| A scripting technique where scripts are structured into scenarios which represent use cases of the software under test. The scripts can be parameterized with test data. |
|
|
Term
|
Definition
| A scripting technique that builds and utilizes a library of reusable (parts of) scripts. |
|
|
Term
|
Definition
The layer in a test automation architecture which provides the necessary code to adapt test scripts on an abstract level to the various components, configuration or interfaces
of the SUT. |
|
|
Term
|
Definition
A realization/implementation of a test automation architecture, i.e., a combination of components implementing a specific test automation assignment. The components may
include commercial off-the-shelf test tools, test automation frameworks, as well as test hardware. |
|
|
Term
|
Definition
The layer in a generic test automation architecture which supports test implementation by supporting the definition of test suites and/or test cases, e.g., by offering templates
or guidelines. |
|
|
Term
|
Definition
| The layer in a generic test automation architecture which supports the execution of test suites and/or test cases. |
|
|
Term
|
Definition
| The layer in a generic test automation architecture which supports manual or automated design of test suites and/or test cases. |
|
|
Term
|
Definition
| A factor that could result in future negative consequences. |
|
|
Term
|
Definition
Synonyms: risk control
The process through which decisions are reached and protective measures are implemented for reducing risks to, or maintaining risks within, specified levels.
|
|
|
Term
|
Definition
See Also: product risk, project risk, risk, risk impact, risk level, risk likelihood
The process of identifying and subsequently analyzing the identified project or product risk to determine its level of risk, typically by assigning likelihood and impact ratings.
risk mitigation
|
|
|
Term
|
Definition
See Also: risk
A risk directly related to the test object.
|
|
|
Term
| automation code defect density |
|
Definition
See Also: defect density
Defect density of a component of the test automation code. |
|
|
Term
|
Definition
Synonyms: test coverage
The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite.
|
|
|
Term
|
Definition
A two-dimensional table, which correlates two entities (e.g., requirements and test cases). The table allows tracing back and forth the links of one entity to the other, thus
enabling the determination of coverage achieved and the assessment of impact of proposed changes. |
|
|
Term
| equivalent manual test effort (EMTE) |
|
Definition
| Effort required for running tests manually. |
|
|
Term
|
Definition
metric
A measurement scale and the method used for measurement. |
|
|
Term
|
Definition
Synonyms: test recording
The process of recording information about tests executed into a test log. |
|
|
Term
|
Definition
See Also: test process
Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders. |
|
|
Term
|
Definition
Synonyms: re-testing
Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.
coverage
|
|
|
Term
|
Definition
Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of
the changes made. It is performed when the software or its environment is changed. |
|
|
Term
|
Definition
Ref: ISO 9000
Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
|
|
|
Term
|
Definition
Ref: IEEE 1219
Modification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.
metric
|
|
|
Term
|
Definition
See Also: authentication
Permission given to a user or process to access resources. |
|
|
Term
|
Definition
| Testware used in automated testing, such as tool scripts. |
|
|
Term
|
Definition
Ref: ISO 9126
The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a
changed environment. |
|
|
Term
|
Definition
The final verdict on the execution of a test and its outcomes, such as pass, fail, or error. The result of error is used for situations where it is not clear whether the problem is in
the test object. |
|
|
Term
| test execution automation |
|
Definition
The use of software, e.g., capture/playback tools, to control the execution of tests, the comparison of actual results to expected results, the setting up of test preconditions, and
other test control and reporting functions. |
|
|
Term
|
Definition
A tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, scheduling of tests, the
logging of results, progress tracking, incident management and test reporting. |
|
|
Term
|
Definition
Ref: ISO 9126
See Also: maintainability
The capability of the software product to enable modified software to be tested.
|
|
|
