Chapter 1 terminology

Question 0

Defect

Answer 0

A flaw in a component or system that can cause the component or system to fail to perform its required function. A defect if encountered during execution may cause a failure of the component or system.

Question 1

Bug

Answer 1

See defect

Question 2

Error

Answer 2

(Mistake): A human action that produces an incorrect result

Question 3

Fail

Answer 3

A test is deemed to fail if it’s actual result does not match its expected result.

Question 4

False fail result

Answer 4

A test result in which a defect is reported although no such defect actually exists in the test object.

Question 5

False positive result

Answer 5

See false fail result

Question 6

Failure

Answer 6

Deviation of the component or system from its expected delivery, service or result.

Question 7

Fault

Answer 7

Defect or bug

Question 8

Mistake

Answer 8

See error

Question 9

Pass

Answer 9

A test is deemed to pass if it s actual result matches its expected result.

Question 10

False negative result

Answer 10

A test result which fails to identify the presence of a defect that is actually present in the test object.

Question 11

Quality

Answer 11

The degree to which a component system or process meets specified requirements and or user/ customer needs and expectations.

Question 12

Risk

Answer 12

A factor that could result in future negative consequences, usually expressed as impact or likelihood.

Question 13

Testing

Answer 13

The process consisting of all life cycle activities both static and dynamic, concerned with planning preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.

Question 14

Requirements

Answer 14

A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed document

Question 15

Review

Answer 15

An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples, management review, informal review, technical review, inspection and walk through

Question 16

Debugging

Answer 16

The process of finding analyzing and removing the causes of failures in software

Question 17

Confirmation testing

Answer 17

Testing that runs test cases that failed the last time they were run in order to verify the success of corrective actions

Question 18

Test strategy

Answer 18

A high-level description of the test levels to be performed and the testing within those levels for an organization or program (One or more projects).

Question 19

Exhaustive testing

Answer 19

A test approach in which the test sweet comprises all combinations of input values and preconditions.

Question 20

Test execution

Answer 20

The process of running a test on the component or system under test, producing actual results.

Question 21

Test approach

Answer 21

The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) projects goal and the risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and types to be performed.