Glossary all terms 3.1 / Glossary all terms 3.1: T

Власник перекладу встановив такі правила доступу, що ви не можете переглядати чужі варіанти перекладів тут.
Оригінал англійською Переклад українською

technical review

#1

test

#2

test adaptation layer
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.

#3

test analysis

#4

test approach

#5

test architect
(1) A person who provides guidance and strategic direction for a test organization and for its relationship with other disciplines. (2) A person who defines the way testing is structured for a given system, including topics such as test tools and test data management.

#6

test automation

#7

test automation architecture
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.

#8

test automation engineer
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.

#10

test automation framework
A tool that provides an environment for test automation. It usually includes a test harness and test libraries.

#11

test automation manager
A person who is responsible for the planning and supervision of the development and evolution of a test
automation solution.

#12

test automation solution
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.

#13

test automation strategy
A high-level plan to achieve long-term objectives of test automation under given boundary conditions.

#14

test basis

#15

test case

#16

test case explosion
The disproportionate growth of the number of test cases with growing size of the test basis, when using a certain test design technique. Test case explosion may also happen when applying the

#17

test design technique
systematically for the first time.

#18

test case result
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.

#19

test case specification

#20

test charter

#21

test closure

#22

test comparator

#23

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

#24

test condition

#25

test control

#26

test cycle
Execution of the test process against a single identifiable release of the test object.

#27

test data

#28

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

#29

test data preparation tool

#30

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

#31

test deliverable
See Also: deliverable
Any test (work) product that must be delivered to someone other than the test (work) product's author.

#32

test design

#33

test design specification

#34

test design technique

#35

test design tool

#36

test director
See Also: test manager
A senior manager who manages test managers.

#37

test environment

#38

test estimation

#39

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

#40

test execution

#41

test execution automation
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.

#42

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

#43

test execution phase
Ref: IEEE 610
The period of time in a software development lifecycle 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.

#44

test execution schedule

#45

test execution technique
The method used to perform the actual test execution, either manual or automated.

#46

test execution tool

#47

test generation layer
The layer in a generic test automation architecture which supports manual or automated design of test suites and/or test cases

#48

test harness

#49

test hook
A customized software interface that enables automated testing of a test object.

#50

test implementation

#51

Наступна сторінка →

Хвилинку...