definitons

Question 1

Checks if everything works as planned

Answer 1

Testing

Question 2

Fixes things when they don’t work as planned

Answer 2

Debugging

Question 3

A fundamental reason for the occurrence of a problem; can be addressed, removed to prevent or reduce frequency of failures or defects

Answer 3

Root cause

Question 4

Mistake made by a human

Answer 4

Error

Question 5

An issue identified in the system

Answer 5

Defect

Question 6

When a defect causes the system to not work as expected

Answer 6

Failure

Question 7

Defines test objects and selects an approach to achieve them

Answer 7

Test planning

Question 8

Ongoing checking of all test activities and comparison of actual progress against the plan

Answer 8

Test monitoring and control

Question 9

Analyzing the test basis to identify testable features, define and prioritize associated test conditions, risks, risk levels

Answer 9

Test analysis

Question 10

Elaborates test conditions into test cases and other testware

Answer 10

Test design

Question 11

Creating or acquiring the necessary testware for test execution

Answer 11

Test implementation

Question 12

Running tests according to the test execution schedule

Answer 12

Test execution

Question 13

Occurs at project milestones for any unresolved defects, change requests, or product backlog items created

Answer 13

Test completion

Question 14

Directs coding through test cases; tests are written first, code is written to satisfy tests, and then both are refactored

Answer 14

Test-Driven Development (TDD)

Question 15

Derives tests from acceptance criteria as part of the system design process; tests are written before the application part is developed to satisfy the tests

Answer 15

Acceptance Test-Driven Development (ATDD)

Question 16

Expresses desired behavior of an application with test cases written in a simple form of natural language (Given/When/Then format); test cases are automatically translated into executable tests

Answer 16

Behavior-Driven Development (BDD)

Question 17

Principle of early testing in SDLC; reviewing specifications from a testing perspective, writing test cases before code, using CI/CD for fast feedback and automated component tests, completing static analysis before dynamic testing, performing non-functional testing at component test level

Answer 17

Shift-left approach

Question 18

Focuses on testing components in isolation

Answer 18

Component testing

Question 19

Focuses on testing interfaces and interactions between components

Answer 19

Component integration testing

Question 20

Focuses on overall behavior and capabilities of an entire system or product, including functional and non-functional testing

Answer 20

System testing

Question 21

Focuses on testing interfaces of the system under test and other systems/services

Answer 21

System integration testing

Question 22

Focuses on validation and demonstrating readiness for deployment, ensuring the system fulfills user’s business needs

Answer 22

Acceptance testing

Question 23

Evaluates functions a component/system should perform (what the test object should do)

Answer 23

Functional testing

Question 24

Evaluates attributes other than functional characteristics (how well system behaves); includes performance, compatibility, usability, reliability, security, maintainability, portability

Answer 24

Non-functional testing

Question 25

Specification-based testing that checks system's behavior against its specifications

Answer 25

Black-box testing

Question 26

Structure-based testing that derives tests from the system's implementation or internal structure

Answer 26

White-box testing

Question 27

Confirms that an original defect has been successfully fixed by executing test cases that previously failed due to the defect and adding new tests for any necessary changes.

Answer 27

Confirmation testing

Question 28

Confirms that no adverse consequences have been caused by a change, including a fix that has already been confirmation tested.

Answer 28

Regression testing

Question 29

Testing that can be corrective, adaptive to changes in the environment, or aimed at improving performance or maintainability. It includes triggers like modifications, upgrades, migrations, and retirement.

Answer 29

Maintenance testing

Question 30

Process of defining the scope of review, work product to review, quality characteristics to be evaluated, areas to focus on, exit criteria, standards, etc.

Answer 30

Planning

Question 31

Ensuring that everyone and everything involved is prepared to start the review process.

Answer 31

Review initiation

Question 32

Assessing the quality of the work product under review individually, identifying anomalies, recommendations, and questions using review techniques.

Answer 32

Individual review

Question 33

Process of deciding the status, ownership, and required actions for each anomaly identified during the review.

Answer 33

Communication and analysis

Question 34

Creating a defect report for every defect found during the review to ensure corrective actions are followed up.

Answer 34

Fixing and reporting

Question 35

Individual who decides what is to be reviewed and provides necessary resources for the review process.

Answer 35

Manager

Question 36

Creates and fixes the work product under review.

Answer 36

Author

Question 37

Ensures the effective running of review meetings during the review process.

Answer 37

Moderator

Question 38

Collates anomalies from reviewers and records review information.

Answer 38

Scribe

Question 39

Individual responsible for performing reviews of work products.

Answer 39

Reviewer

Question 40

Individual who takes overall responsibility for the review process.

Answer 40

Review leader

Question 41

Review process without a defined process or formal documentation output.

Answer 41

Informal review

Question 42

Review led by the author to evaluate quality, educate reviewers, gain consensus, and motivate the author.

Answer 42

Walkthrough

Question 43

Review performed by technically qualified reviewers and led by a moderator to make decisions regarding technical problems.

Answer 43

Technical review

Question 44

Most formal type of review following a complete generic process with the main objective of finding the maximum number of anomalies.

Answer 44

Inspection

Question 45

Utilizing the knowledge and experience of testers to effectively implement test cases and detect defects that may be missed by other testing methods.

Answer 45

Experience-based testing

Question 46

Coverage items are executable statements

Answer 46

Statement testing

Question 47

Transfer of control between two nodes in the control flow graph

Answer 47

Branch

Question 48

Coverage items are branches; aim is to design test cases to exercise branches

Answer 48

Branch testing

Question 49

Technique to anticipate errors based on tester's knowledge

Answer 49

Error guessing

Question 50

Simultaneously design, execute, and evaluate tests while learning about the test object

Answer 50

Exploratory testing

Question 51

Tester designs, implements, and executes tests based on a checklist

Answer 51

Checklist-based testing

Question 52

Represents a feature valuable to a user or purchaser of a system

Answer 52

User story

Question 53

Looks ahead to the end of a single iteration; concerned with the iteration backlog

Answer 53

Iteration planning

Question 54

Looks ahead to the release of a product; defines and re-defines the product backlog

Answer 54

Release planning

Question 55

Preconditions for undertaking a given activity

Answer 55

Entry criteria

Question 56

Defines what must be achieved to declare an activity complete

Answer 56

Exit criteria

Question 57

Pull from data and past experiences

Answer 57

Estimation based on ratios

Question 58

Pull from past experiences

Answer 58

Extrapolation

Question 59

Method using experts for estimation

Answer 59

Wideband Delphi

Question 60

Estimate calculation using optimistic, likely, and pessimistic values

Answer 60

Three-point estimation

Question 61

Prioritization methods include risk-based, coverage-based, and requirements-based

Answer 61

Test case prioritization

Question 62

Model showing different granularity levels of tests

Answer 62

Test pyramid

Question 63

Probability of risk occurrence

Answer 63

Risk likelihood

Question 64

Consequences of risk occurrence

Answer 64

Risk impact

Question 65

Include organizational, people, technical, and supplier issues

Answer 65

Project risks

Question 66

Include user dissatisfaction, revenue loss, trust damage, maintenance costs, criminal penalties, damages

Answer 66

Product risks