Glossar - Viconnis Test-Technologie GmbH

test comparisonThe process of identifying differences between the actual results produced by the software under test and the expected results for a test case. Test comparison can be performed during test execution (dynamic comparison) or after test execution.

test completion criteriaSee exit criteria.

test conditionAn item or event of a component or system that could be verified by one or more test cases, e.g. a function, transaction, feature, quality attribute, or structural element.

test controlA test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned. See also test management.

test coverageSee coverage.

test cycleExecution of the test process against a single identifiable release of the test object.

test dataData that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.

test data managementThe process of analyzing test data requirements, designing test data structures, creating and maintaining test data.

test data preparation toolA type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.

test definition layerThe 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.

test deliverableAny test (work) product that must be delivered to someone other than the test (work) product’s author. See also deliverable.

Test der RessourcennutzungTesten, um die Ressourcennutzung eines Softwareprodukts festzustellen. Siehe auch Effizienztest.

test design(1) See test design specification. (2) The process of transforming general test objectives into tangible test conditions and test cases.

test design specificationA document specifying the test conditions (coverage items) for a test item, the detailed test approach and identifying the associated high-level test cases. [After IEEE 829] See also test specification.

test design techniqueA method used to derive or select test cases.

test design toolA tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository, e.g. requirements management tool, or from specified test conditions held in the tool itself, or from code.

test directorA senior manager who manages test managers. See also test manager.

test-driven developmentA way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases.

test driverSee driver.

test environmentAn environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test [after IEEE 610].

test estimationThe calculated approximation of a result related to various aspects of testing (e.g. effort spent, completion date, costs involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy.

test evaluation reportA document produced at the end of the test project summarizing all testing activities and results. It also contains an evaluation of the test process and lessons learned.

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

test execution automationThe use of software, e.g. capture/playback tools, to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and reporting functions.

test execution layerThe layer in a generic test automation architecture which supports the execution of test suites and/or test cases.

test execution phaseThe period of time in a software development life cycle during which the components of a software product are executed, and the software product is evaluated to determine whether or not requirements have been satisfied [IEEE 610].

test execution scheduleA scheme for the execution of test procedures. Note: The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.

test execution techniqueThe method used to perform the actual test execution either manually or automated.

test execution toolA type of test tool that is able to execute other software using an automated test script, e.g. capture/playback.

test failSee fail.