ISTQB-TAE Definitions Flashcards

1
Q

API testing

A

Testing performed by submitting commands to the software under test using programming interfaces of the application directly.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

CLI testing

A

Testing performed by submitting commands to the software under test using a dedicated command-line interface.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

GUI testing

A

Testing performed by interacting with the software under test via the graphical user interface.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

System Under Test

A

A type of test object that is a system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Test automation architecture

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Test automation framework

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Test automation strategy

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Test automation

A

The use of software to perform or support test activities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Test script

A

A sequence of instructions for the execution of a test.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Testware

A

Work products produced during the test process for use in planning, designing, executing, evaluating, and reporting on testing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Testability

A

The degree to which test conditions can be established for a component or system, and tests can be performed to determine whether those test conditions have been met.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Driver

A

A temporary component or tool that replaces another component and controls or calls a test item in isolation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Level of intrusion

A

The level to which a test object is modified by adjusting it for testability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Stub

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Test execution tool

A

A test tool that executes tests against a designated test item and evaluates the outcomes against expected results and postconditions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Test hook

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Test automation manager

A

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

18
Q

Capture/playback

A

A test automation approach in which inputs to the test object are recorded during manual testing to generate automated test scripts that can be executed later.

19
Q

Data-driven testing

A

A scripting technique that uses data files to contain the test data and expected results needed to execute the test scripts.

20
Q

Generic test automation architecture (gTAA)

A

Representation of the layers, components, and interfaces of a test automation architecture, allowing for a structured and modular approach to implement test automation.

21
Q

Keyword-driven testing

A

A scripting technique in which test scripts contain high-level keywords and supporting files that contain low-level scripts that implement those keywords.

22
Q

Linear scripting

A

A simple scripting technique without any control structure in the test scripts.

23
Q

Model-based testing

A

Testing based on or involving models.

24
Q

Process-driven scripting

A

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.

25
Q

Structured scripting

A

A scripting technique that builds and utilizes a library of reusable (parts of) scripts.

26
Q

Test adaptation layer

A

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.

27
Q

Test automation solution

A

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.

28
Q

Test definition layer

A

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.

29
Q

Test execution layer

A

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

30
Q

Test generation layer

A

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

31
Q

Risk

A

A factor that could result in future negative consequences.

32
Q

Risk mitigation

A

The process through which decisions are reached and protective measures are implemented for reducing or maintaining risks to specified levels.

33
Q

Risk assessment

A

The process to examine identified risks and determine the risk level.

34
Q

Product risk

A

A risk impacting the quality of a product.

35
Q

Automation code defect density

A

Defect density of a component of the test automation code.

36
Q

Coverage

A

The degree to which specified coverage items have been determined or have been exercised by a test suite expressed as a percentage.

37
Q

Traceability matrix

A

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.

38
Q

EMTE

A

(Equivalent manual test effort) Effort required for running tests manually.

39
Q

Metrics

A

A measurement scale and the method used for measurement.

40
Q

Test logging

A

The activity of creating a test log.

41
Q

Test reporting

A

Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders.

42
Q

Verification

A

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