Brainscape's Knowledge GenomeTM

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


See full index

Ss > Gg > Flashcards

Gg Flashcards

1
Q

difference between testing and debugging

A

Testing can trigger failures in dynamic testing /static testing ., then debugging deals with it

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

debugging involves (3)

A

Reproduction of a failure • Diagnosis (finding the root cause) • Fixing the cause

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

Subsequent confirmation testing checks…

A

the fixes resolved the problem

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

Subsequent regression testing

A

to check whether the fixes are causing failures in other parts

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

When static testing identifies a defect, debugging….

A

concerned with removing I, no need to reproduce

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

when dynam testing triggers a failure debugging has to

A

has to find the cause, analyze and eleminate

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

Testing is a form of quality control (QC). QC is…

A

product oriented, supporting the achievement of appropriate levels of quality

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

QA is

A

a process-oriented,preventive approach,improvement of processes

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

how QC uses test results…

A

used to fix defects

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

how QA uses test results…

A

provide feedback

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

errors and defects are cause of …

A

failures

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

A root cause is a…

A

reason for the occurrence of a problem

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

Root causes are identified through..

A

root cause analysis

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

when root cause analysis is performed?(2)

A

when a failure occurs defect is identified.

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

testing principles(7)

A

1 testing shows presence of defects 2 testing everything impossible (exhaustive testing) 3early testing saves time and money 4Defects cluster together. 5. Tests wear out 6Testing is context dependent. 7Absence-of-defects misconception

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

to overcome the wear out of tests…

A

existing tests and test data may need to be modified, and new tests may need to be written

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

testing activities(7)

A

1planning 2monitoring/control 3analysis 4design 5implementation 6execution 7completion

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

Testware is created as

A

output work products from the test activities

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

to implement effective test monitoring and control

A

establish and maintain traceability

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

test management role takes overall responsibility for

A

test process,

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

test management role is mainly focused on the activities of

A

test planning, test monitoring and control and test completion

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

testing role takes overall responsibility for the

A

engineering (technical) aspect of testing.

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

testing role is mainly focused on the activities of

A

test analysis, test design, test implementation and test execution

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

whole-team approach

A

any team member with the necessary knowledge and skills can perform any task, and everyone is responsible for quality.

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

In sequential development testers

A

participate in requirement reviews, test analysis, and test design.

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

in iterative and incremental development models testing

A

each iteration both static and dynamic testing

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

manual testing tends to be done using

A

experience-based test techniques that dont require prior test analysis and design.

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

good practices in any SDLC (4)

A

1.For every software development activity-corresponding test activity 2.Different test levels - different test objectives, 3.Test analysis and design in early testing 4.Testers are involved in draft documentation

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

TDD

A

Directs the coding through test cases, tests written first

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

ATDD

A

Derives tests from acceptance criteria, Tests are written before the part of the application

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

BDD

A

test cases written in natural language first

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

DevOps promotes

A

CI / CD

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

Although DevOps comes with a high level of automated testing, manual testing…

A

will still be needed.

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

shift left?

A

early testing in SDLC

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

Retrospectives?

A

end of a project or an iteration meetings

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

Results after retrospective…

A

part of the test completion report

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

test levels-

A

groups of test activities that are organized and managed together.

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

Each test level is

A

instance of the test process

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

sequential SDLC models, the test levels

A

defined such that the exit criteria of one level are part of the entry criteria for the next level.

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

Test types are

A

groups of test activities related to specific quality characteristics

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

test levels (5)

A

componenet component integration system system integration acceptance

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

component Testing level

A

tesing components in isolation

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

component integration testing level

A

testing interfaces and interactions between components

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

System Testing level

A

overall behavior and capabilities of an entire system

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

system integration Testing level

A

testing the interfaces of the system under test and other systems and external services

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

acceptance Testing level

A

demonstrating readiness for deployment,

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

system testing level includes (2)

A

1.functional testing of end-to-end tasks 2.the non-functional testing of quality characteristics

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

acceptance testing level forms(5)

A
  1. UAT testing 2. operational 3. regulatory 4.alpha 5.beta
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

Test levels are distinguished by attributes (5)

A

test obejct test objective basis defects approach/responsibilities

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

test types (4)

A

functional non functional black box white box

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

f. Testing type

A

evaluates the functions that a component or system should perform ‘what’ object should do

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

n.f.testing type

A

non-functional software quality characteristics.“how well the system behaves”

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

black box Testing type

A

specification-based

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

white box Testing Type

A

structure-based

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

confirmation tesing

A

original defect has been successfully fixed

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

how to do confirmation test (2)

A

1.executing all test cases that previously have failed 2.adding new tests to cover any changes

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

after maintenance regression testing makes sure that…

A

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

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

before regression test

A

perform impact analysis

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

maintenance involve what realeases?

A

planned releases and unplanned(hotfix)

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

before maintenance change is made need to do

A

impact analysis

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

testing the changes to a system in prod includes(2)

A

1evaluating success of implement of change 2checking for regression in parts that didnt change

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

scope of maintenance depends on (3)

A

1degree of risk 2size of system 3size of change

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

triggers for maintenance (3)

A

1modifications 2upgrades/migrations 3retirement of sys

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

after retirment/archiving the sys, testing of ….needed

A

restore and retrieval procedures

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

work products are evaluated through…

A

manual examination (reviews)

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

static t. objectives

A

improving quality, assessing characteristics like readability, completeness,

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

static t, can be applied to v…and v…

A

verification and validation

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

the Definition of Ready Review techniques

A

to ensure user stories are complete and understandable and include testable acceptance criteria.

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

Static analysis can identify problems prior to

A

dynamic test.

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

during static analysis we use

A

no test cases are required, and tool are typically used.

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

Almost any work product can be examined using

A

static t

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

work pr testing with static t. needs to

A

work products need a structure against which they can be checked

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

Work products that are not appropriate for static testing

A

that are difficult to interpret by human beings and that should not be analyzed by tools ( legal reasons).

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

value of static t.

A

detect defects early and defects which cannot be detected by dynamic testing

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

difference between static and dynamic(5)

A
  1. both detect defects but of diff types can be found by either 2. static finds defects directly while dynamic causes failures 3.static find decets that lay on paths through the code that are rarely executed 4. static to non executable work products 5.static measure quality characteristics that are not dependant on executing code
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
76
Q

defects that are easier to find through static testing(7)

A

req def design def coding def deviations of stand security vulnerab gaps in test coverage

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

ISO/IEC 20246 standard defines a

A

review process

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

activities in the review process(5)

A

planning review initiation individual review communication and analysis fixing and reporting

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

roles in reviews(6)

A

manager author moderator scribe reviewer review leader

80
Q

manager’s role in reviews

A

decides what is to be reviewed and provides resources

81
Q

author’s role in reviews

A

creates and fixes the work product under review

82
Q

moderator’s role in reviews

A

– ensures the effective running of review meetings

83
Q

scribe’s role in reviews

A

collects anomalies from reviewers

84
Q

reviewer’s role in reviews

A

performs reviews.

85
Q

review leader’s role in reviews

A

overall responsibility- who where when reviewing

86
Q

review types(4)

A

informal review walkthrough technical review inspection

87
Q

informal review type

A

main objective is detecting anomalies. dont follow a process

88
Q

walkthrough review type

A

led by author. evaluating quality and building confidence in the work product, educating reviewers

89
Q

Technical Review type

A

led by a moderator. gain consensus and make decisions regarding a technical problem,

90
Q

Inspection review type

A

main objective is to find the maximum number of anomalies.

91
Q

black box test techniques(4)

A

Equivalence Partitioning • Boundary Value Analysis • Decision Table Testing • State Transition Testing

92
Q

Equivalence Partitioning (EP)

A

divides data into partitions,to be processed in the same way by the test object.

93
Q

Equivalence partitions can be identified for any data element related to…(7)

A

the test object, including inputs, outputs, configuration items, internal values, time-related values, interface parameters

94
Q

types of EP partitions(2)

A

valid values invalid values

95
Q

valid values partition

A

should be processed by the test object or as those for which the specification defines

96
Q

invalid values partition

A

should be ignored or rejected values or no processing is defined in specification

97
Q

Each Choice coverage ?

A

simplest coverage criterion in the case of multiple sets of partitions

98
Q

Each Choice coverage requires test cases to?

A

to exercise each partition from each set of partitions at least once.

99
Q

Boundary Value Analysis

A

exercising the boundaries of equivalence partitions

100
Q

BVA can only be used for..

A

ordered partitions

101
Q

boundry values?

A

the minimum and maximum values of a partition

102
Q

BVA, if two elements belong to the same partition..

A

all elements between them must also belong to that partition

103
Q

2-value BVA

A

two coverage items: this boundary value and its closest neighbor

104
Q

3-value BVA

A

three coverage items: this boundary value and both its neighbors

105
Q

Decision tables

A

r testing the implementation of system requirements that specify how different combinations of conditions result in different outcomes

106
Q

state transition diagram

A

behavior of a system by showing its possible states and valid state transitions.

107
Q

in state transition diagram, transition is initiated by…

A

event

108
Q

in state transition diagram, transitions are assumed to be…(2)

A

to be instantaneous may sometimes result in the software taking action

109
Q

in State Transition Testing , state table?

A

model equivalent to a state transition diagram

110
Q

coverage criterias for state transition testing (3)

A

all states coverage valid transitions coverage all transitions coverage

111
Q

all states coverage

A

the coverage items are the states

112
Q

valid transitions coverage

A

coverage items are single valid transitions

113
Q

all transitions coverage

A

coverage items are all the transitions shown in a state table.

114
Q

statement testing coverage items

A

executable statements

115
Q

statement t. aim to design test cases that..

A

that exercise statements in the code until an acceptable level of coverage is achieved

116
Q

statement t.- when 100proc statement coverage is acheved it ensures..

A

it ensures that all executable statements been exercised at least once

117
Q

statement t. - each statement with a defect will be executed, which may cause…

A

may cause a failure demonstrating the presence of the defect.

118
Q

statement t. - when it may not detect defect?

A

if its data dependent

119
Q

A branch is

A

a transfer of control between two nodes in the control flow graph

120
Q

control flow graph shows

A

the possible sequences in which source code statements are executed

121
Q

Each transfer of control can be either… (2)

A

conditional unconditional

122
Q

Conditional branches typically correspond to a.. (2)

A

true/false outcome a decision to exit /conrinue

123
Q

Branch t.- may not detect defects that require

A

the execution of a specific path in a code.

124
Q

strenght of white box t.

A

entire software implementation is taken into account during testing

125
Q

weakness of white box t.

A

if the software does not implement one or more requirements, white box testing may not detect defects

126
Q

if white box does not detect defect, it may result in

A

defects of omission

127
Q

White-box coverage measures provide an…. (2)

A

objective measurement of coverage nformation to allow additional tests to be generated

128
Q

experience based test techniques 3

A

Error guessing • Exploratory testing • Checklist-based testing

129
Q

In general, errors, defects and failures may be related to: …. (5)

A

input output logic camputation data

130
Q

Fault attacks are a methodical approach to…

A

to the implementation of error guessing

131
Q

how to do Fault attacks 2 steps

A
  1. tester to create or acquire a list of possible errors 2.design tests that will identify defects associated with the errors
132
Q

exploratory testing

A

tests are simultaneously designed, executed, and evaluated while the tester learns about the test object

133
Q

exploratory t. conducted using

A

session-based testing

134
Q

In a session-based approach for explo testing 3

A

1.its within a defined timebox 2. tester uses a test charter 3. in the end discussion between the tester and stakeholders

135
Q

Exploratory testing is useful when 2

A

there are few specifications time pressure

136
Q

checklist-based testing

A

a tester designs, implements, and executes tests from a checklist.

137
Q

Checklists should not contain items that…3

A

1 items that can be checked automatically, 2 items better suited as entry/exit criteria, 3 items that are too general

138
Q

Collaboration-based approaches

A

focus on defect avoidance by collaboration and communication.

139
Q

User stories critical aspects 3

A

card coversation confirmation

140
Q

Collaborative authorship of the user story can use techniques such as….2

A

brainstorming mind mapping

141
Q

Acceptance criteria for a user story are

A

conditions that an implementation must meet to be accepted by stakeholders.

142
Q

ways to write acceptance criteria for a user story 2

A

scenario oriented rule oriented

143
Q

ATDD steps 2

A
  1. specification workshop . acceptance criteria written 2. create test cases
144
Q

ATDD test cases must cover…

A

all the characteristics of the user story and should not go beyond the story

145
Q

In iterative SDLCs, kinds of planning 2

A

release planning iteration planning.

146
Q

If entry criteria are not met…

A

activity will prove to be more difficult, time-consuming, costly, and riskier

147
Q

Typical entry criteria include: 3

A

availability of resources availability of testware initial quality of object

148
Q

Typical exit criteria include 2

A

measures of thoroughness completion criteria

149
Q

In Agile software development, exit criteria are often called

A

Definition of Done

150
Q

Definition of Ready.

A

Entry criteria that a user story must fulfill to start the development and/or testing

151
Q

Test effort estimation

A

predicting the amount of test-related work needed

152
Q

estimation techniques 4

A

Estimation based on ratios Extrapolation Wideband Delphi. Three-point estimation

153
Q

Estimation based on ratios

A

figures are collected from previous projects within the organization, which makes it possible to derive “standard” ratios for similar projects

154
Q

Extrapolation

A

measurements are made as early as possible in the current project to gather the data.. This method is very suitable in iterative SDLCs

155
Q

Wideband Delphi

A

experts make experience-based estimations. Each expert, in isolation, estimates the effort.

156
Q

Three-point estimation

A

hree estimations are made by the experts: the most optimistic estimation (a), the most likely estimation (m) and the most pessimistic estimation (b)

157
Q

test case prioritization strategies 3

A

Risk-based prioritization Coverage-based prioritization Requirements-based prioritization

158
Q

Risk-based prioritization

A

order of test execution is based on the results of risk analysis.the most important risks are executed first.

159
Q

Coverage-based prioritization

A

order of test execution is based on coverage.Test cases achieving the highest coverage are executed first

160
Q

Requirements-based prioritization

A

Test cases related to the most important requirements are executed first.

161
Q

Test Pyramid

A

a model showing that different tests may have different granularity

162
Q

test pyramid layers

A

The higher the layer, the lower the test granularity, test isolation and test execution time. Tests in the bottom layer are small, isolated, fast, and check a small piece of functionality

163
Q

The testing quadrants

A

group the test levels with the appropriate test types, activities, test techniques and work products in the Agile software development.

164
Q

Testing Quadrants model supports test management in…

A

visualizing groups to ensure that all appropriate test types and test levels are included in the SDLC

165
Q

In Testing Quadrants model, tests can be 2

A

business facing technology facing

166
Q

Quadrant Q1( technology facing, support the team)

A

contains component and component integration tests. These tests should be automated and included in the CI process.

167
Q

Quadrant Q2 (business facing, support the team)

A

contains functional tests,These tests check the acceptance criteria and can be manual or automated.

168
Q

Quadrant Q3 (business facing, critique the product).

A

contains exploratory testing,These tests are user-oriented and often manual.

169
Q

Quadrant Q4 (technology facing, critique the product).

A

contains smoke tests and non-functional tests,These tests are often automated.

170
Q

risk management activities 2

A

Risk analysis Risk control

171
Q

risk-based testing

A

test activities are selected and managed based on risk analysis and risk control

172
Q

A risk can be characterized by factors: 2

A

Risk likelihood Risk impact

173
Q

types of risks 2

A

project risks product risks

174
Q

when project risk occurs , it has impact on

A

have an impact on the project schedule, budget or scope

175
Q

Product risk analysis consists of… 2

A

risk identification risk assessment

176
Q

Risk assessment approaches 3

A

quantitative qualitative mix of them

177
Q

quantitative risk assesment approach

A

risk level =multiplication of risk likelihood and risk impact.

178
Q

qualitative risk assesment approach

A

the risk level can be determined using a risk matrix.

179
Q

Product risk control consists of…2

A

risk mitigation risk monitoring

180
Q

Actions that can be taken to mitigate the product risks by testing are 6

A

testers with level of experience/skills appropriate level of independence of testing reviews and static analysis appropriate test techniques and coverage levels appropriate test types doe quality characteristics dynamic testing, regression testing

181
Q

Test monitoring information is used to…

A

to assess test progress and test exit criteria/test tasks satisfied

182
Q

Test control uses the information from test monitoring to provide…

A

guidance and the necessary corrective actions

183
Q

Test completion collects data from completed test activities to…

A

to consolidate experience, testware

184
Q

Test completion activities occur…

A

at project milestones

185
Q

Test monitoring gathers a variety of metrics to…

A

to support the test control and test completion.

186
Q

Test reporting-

A

summarizes and communicates test information during and after testing

187
Q

Test completion reports-

A

summarize a specific stage of testing

188
Q

During test monitoring and control, the test team generates..

A

generates test progress reports for stakeholders to keep them informed

189
Q

difference reporting on test progress and completion

A

progress=is frequent and informal completion= follows a set template and occurs only once.

190
Q

configuration management

A

for identifying, controlling, and tracking work products such as test plans…

191
Q

For a complex configuration item (test env), configuration managment…

A

records the items it consists of, their relationships, and versions

192
Q

If the configuration item is approved for testing….

A

it becomes a baseline and can only be changed through a formal change

193
Q

Configuration management keeps a record of…

A

a record of changed configuration items when a new baseline is created.

194
Q

To properly support testing, Configuration management ensures the following: 2

A

1 All configuration items are uniquely identified, version controlled…so that traceability can be maintained 2 All identified items referenced in test doc

195
Q

defect management process includes a…2

A

1 includes a workflow for handling individual anomalies from their discovery to their closure 2 rules for their classification

Ss (1 decks)

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