ISTQB CTFL V.4 Keywords Chapter 1

0.0(0)
studied byStudied by 1 person
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/27

flashcard set

Earn XP

Description and Tags

Keywords taken directly from the CTFL v.4 syllabus and looked up from the ISTQB glossary. I've also added the simplified definition.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

28 Terms

1
New cards

Coverage

The degree to which specified coverage items are exercised by a test suite, expressed as a percentage.

Simplified: How much of the specified items are tested, shown as a percentage.

2
New cards

Debugging

The process of finding, analyzing and removing the causes of failures in a component or system.

Simplified: Finding and fixing problems in a system.

3
New cards

Defect

An imperfection or deficiency in a work product where it doesn’t meet its requirement or specifications.

Simplified: A flaw or mistake in a product that doesn't meet its requirements.

4
New cards

Error

A human action that produces and incorrect result.

Simplified: A mistake made by a person, resulting in incorrect outcomes.

5
New cards

Failure

An event in which a component or system does not perform a required function within specified limits.

Simplified: When a system doesn't perform as expected.

6
New cards

Quality

The degree to which a work product satisfies stated and implied needs of its stakeholders.

Simplified: How well a product meets the needs of its users.

7
New cards

Quality Assurance

Activities focused on providing confidence that quality requirements will be fulfilled.

Simplified: Activities ensuring that quality requirements are met.

8
New cards

Root Cause

A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.

Simplified: The main reason behind a defect.

9
New cards

Test Analysis

The activity that identifies test conditions by analyzing the test basis.

Simplified: Identifying what to test by examining the test basis.

10
New cards

Test Basis

The body of knowledge used as the basis for the test analysis and design.

Simplified: Information used to plan and design tests.

11
New cards

Test Case

A set of preconditions, inputs, actions, expected results and postconditions, developed based on test conditions.

Simplified: A set of steps and conditions to test something.

12
New cards

Test Completion

The activity that makes testware available for later use, leaves test environments in a satisfactory condition and communicates the results of resting to relevant stakeholders.

Simplified: Finalizing testing and reporting results.

13
New cards

Test Condition

A testable aspect of a component or system identified as a basis for testing.

Simplified: Something you can test in a system.

14
New cards

Test Control

The activity that develops and applies corrective actions to get a test project on track when it deviates from what was planned.

Simplified: Adjusting testing to stay on track.

15
New cards

Test Data

Data needed for test execution.

Simplified: Information needed for testing.

16
New cards

Test Design

The activity that derives and specifies test cases from test conditions.

Simplified: Planning how to test based on test conditions.

17
New cards

Test execution

The activity that runs a rest on a component or system producing actual results.

Simplified: Running tests to get actual results.

18
New cards

Test Implementation

The activity that prepares the testware needed for test execution based on test analysis and design.

Simplified: Preparing for test execution.

19
New cards

Test Monitoring

The activity that checks the status of testing activities, identifies any variance from planned or expected, and reports status to stakeholders.

Simplified: Keeping track of testing progress.

20
New cards

Test Object

The work produced to be tested.

Simplified: The thing you're testing.

21
New cards

Test objective

The purpose of testing.

Simplified: Why you're testing something.

22
New cards

Test Planning

The activity of establishing or updating a test plan.

Simplified: Creating a plan for testing.

23
New cards

Test Procedure

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.

Simplified: Steps to execute a test.

24
New cards

Test Result

The consequence or outcome of the execution of a test.

Simplified: Outcome of a test.

25
New cards

Testing

The process within the software development lifecycle that evaluates the quality of component or system and related work products.

Simplified: Evaluating the quality of a system.

26
New cards

Testware

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

Simplified: Documents and tools used for testing.

27
New cards

Validation

Confirmation by examination that a work product matches a stakeholders needs.

Simplified: Checking if a product meets needs.

28
New cards

Verification

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

Simplified: Confirming requirements are met.