Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

ISTQB Definitions > definitons > Flashcards

definitons Flashcards

1
Q

Checks if everything works as planned

A

Testing

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

Fixes things when they don’t work as planned

A

Debugging

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

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

A

Root cause

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

Mistake made by a human

A

Error

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

An issue identified in the system

A

Defect

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

When a defect causes the system to not work as expected

A

Failure

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

Defines test objects and selects an approach to achieve them

A

Test planning

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

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

A

Test monitoring and control

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

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

A

Test analysis

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

Elaborates test conditions into test cases and other testware

A

Test design

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

Creating or acquiring the necessary testware for test execution

A

Test implementation

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

Running tests according to the test execution schedule

A

Test execution

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

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

A

Test completion

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

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

A

Test-Driven Development (TDD)

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

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

A

Acceptance Test-Driven Development (ATDD)

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

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

A

Behavior-Driven Development (BDD)

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

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

A

Shift-left approach

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

Focuses on testing components in isolation

A

Component testing

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

Focuses on testing interfaces and interactions between components

A

Component integration testing

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

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

A

System testing

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

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

A

System integration testing

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

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

A

Acceptance testing

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

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

A

Functional testing

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

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

A

Non-functional testing

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

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

A

Black-box testing

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

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

A

White-box testing

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

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.

A

Confirmation testing

28
Q

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

A

Regression testing

29
Q

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.

A

Maintenance testing

30
Q

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

A

Planning

31
Q

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

A

Review initiation

32
Q

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

A

Individual review

33
Q

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

A

Communication and analysis

34
Q

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

A

Fixing and reporting

35
Q

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

A

Manager

36
Q

Creates and fixes the work product under review.

A

Author

37
Q

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

A

Moderator

38
Q

Collates anomalies from reviewers and records review information.

A

Scribe

39
Q

Individual responsible for performing reviews of work products.

A

Reviewer

40
Q

Individual who takes overall responsibility for the review process.

A

Review leader

41
Q

Review process without a defined process or formal documentation output.

A

Informal review

42
Q

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

A

Walkthrough

43
Q

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

A

Technical review

44
Q

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

A

Inspection

45
Q

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

A

Experience-based testing

46
Q

Coverage items are executable statements

A

Statement testing

47
Q

Transfer of control between two nodes in the control flow graph

A

Branch

48
Q

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

A

Branch testing

49
Q

Technique to anticipate errors based on tester’s knowledge

A

Error guessing

50
Q

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

A

Exploratory testing

51
Q

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

A

Checklist-based testing

52
Q

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

A

User story

53
Q

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

A

Iteration planning

54
Q

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

A

Release planning

55
Q

Preconditions for undertaking a given activity

A

Entry criteria

56
Q

Defines what must be achieved to declare an activity complete

A

Exit criteria

57
Q

Pull from data and past experiences

A

Estimation based on ratios

58
Q

Pull from past experiences

A

Extrapolation

59
Q

Method using experts for estimation

A

Wideband Delphi

60
Q

Estimate calculation using optimistic, likely, and pessimistic values

A

Three-point estimation

61
Q

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

A

Test case prioritization

62
Q

Model showing different granularity levels of tests

A

Test pyramid

63
Q

Probability of risk occurrence

A

Risk likelihood

64
Q

Consequences of risk occurrence

A

Risk impact

65
Q

Include organizational, people, technical, and supplier issues

A

Project risks

66
Q

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

A

Product risks

ISTQB Definitions (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions