1.
What
is
the
main
benefit
of
designing
tests
early?
Answer:
it
stops
defects
being
introduced
into
the
code
(stops
error
of
propagation).
It
also
helps
to
correct
errors
cheaper,
provide
confidence
to
developers
to
code
quickly,
and
eliminate
ambiguity
in
requirements
and
specification.
2.
What
is
risk
based
testing?
Answer:
Prioritizing
tests
based
on
product
and
projects
risk
to
identify
the
test
strategy,
any
non-testing
activities
and
prioritization
of
tests
to
determine
which
tests
to
address
first.
3.
A
wholesaler
sells
printer
cartridges.
The
minimum
order
quantity
is
5.
There
is
a
20%
discount
for
orders
of
100
or
more
printer
cartridges.
You
have
been
asked
to
prepare
test
cases
using
various
values
for
the
number
of
printer
cartridges
ordered.
Which
of
the
following
groups
contain
three
test
inputs
that
would
be
generated
using
Boundary
Value
Analysis?
Answer:
4,5,
99.
4.
What
is
the
key
difference
between
preventive
and
reactive
approach
to
testing
Answer:
Preventive
tests
are
designed
early,
and
reactive
tests
are
designed
after
the
software
has
been
produced.
5.
What
is
the
purpose
of
exit
criteria?
Answer:
when
to
stop
testing,
when
the
test
level
is
finished
when
a
predefined
Level
of
quality
has
been
achieved.
6.
What
determines
the
level
of
risk
?
Answer:
likelihood
of
a
risk
happening
x
impact
of
that
risk.
7.
When
decision
table
testing
is
used
?
Answer:
Decision
table
testing
is
used
for
testing
systems
for
which
the
specification
takes
the
form
of
rules
or
cause-effect
combinations.
In
a
decision
table
the
inputs
are
listed
in
a
column,
with
the
outputs
in
the
same
column
but
below
the
inputs.
The
remainder
of
the
table
explores
combinations
of
inputs
to
define
the
outputs
produced.
8.
What
is
the
main
objective
when
reviewing
software
deliverables?
Answer:
to
identify
defects
in
an
of
the
software
work
products.
9.
Which
of
the
following
defines
the
expected
result
of
a
test
?
Test
cases/test
design
specification
?
Answer:
test
case
specification
defines
the
expected
result.
It
consist
of
input,
execution
pre
condition,
expected
result,
execution
post
condition,
pass/fail,
remarks,
test
procedure
specification
(
step
by
step
instruction).
10.
What
is
the
benefit
of
independence
tests
?
Answer:
it
avoids
author
bias,
false
assumption
and
issues
due
to
objectives.
11.
As
a
part
of
which
test
process
do
you
determine
the
exit
criteria?
Answer:
test
Planning.
12.
What
is
beta
testing
?
Answer:
testing
performed
by
potential
customer
at
their
own
location.
13.
Given
the
following
fragment
of
code,
how
many
tests
are
required
for
100%
decision
coverage?
if
width
>
length
thenbiggest_dimension
=
width
if
height
>
width
thenbiggest_dimension
=
height
end_if
elsebiggest_dimension
=
length
if
height
>
length
thenbiggest_dimension
=
height
end_if
end_if
?
Answer:
4.
14.
You
have
designed
test
cases
to
provide
100%
statement
and
100%
decision
coverage
for
the
following
fragment
of
code.
if
width
>
length
then
biggest_dimension
=
width
else
biggest_dimension
=
length
end_if
The
following
has
been
added
to
the
bottom
of
the
code
fragment
above.
print
"Biggest
dimension
is
"
&biggest_dimensionprint
"Width:
"
&
width
print
"Length:
"
&
length
How
many
more
test
cases
are
required?
Answer:
None.
15.
What
is
Rapid
Application
Development
?
Answer:
Rapid
Application
Development
(RAD)
is
formally
a
parallel
development
of
functions
and
subsequent
integration.
Components/functions
are
developed
in
parallel
as
if
they
were
mini
projects,
the
developments
are
time-boxed,
delivered,
and
then
assembled
into
a
working
prototype.
16.
What
is
the
difference
between
testing
technique
and
testing
tool
?
Answer:
Testing
technique:
Is
a
process
for
ensuring
that
some
aspects
of
the
applications
system
or
unit
functions
properly
there
may
be
few
techniques
but
many
tools.
Testing
Tools:
Is
a
vehicle
for
performing
a
test
process.
The
tool
is
a
resource
to
the
tester,
but
itself
is
insufficient
to
conduct
testing
17.
We
use
the
output
of
the
requirement
analysis,
the
requirement
specification
as
the
input
for
writing
Answer:
User
Acceptance
Test
Cases.
18.
Repeated
Testing
of
an
already
tested
program,
after
modification,
to
discover
any
defects
introduced
or
uncovered
as
a
result
of
the
changes
in
the
software
being
tested
or
in
another
related
or
unrelated
software
component:
Answer:
Regression
Testing.
19.
What
is
component
testing?
Answer:
Component
testing,
also
known
as
unit,
module
and
program
testing,
searches
for
defects
in,
and
verifies
the
functioning
of
software
(e.g.
modules,
programs,
objects,
classes,
etc.)
that
are
separately
testable.
Component
testing
may
be
done
in.
Most
often
stubs
and
drivers
are
used
to
replace
the
missing
software
and
simulate
the
interface
between
the
software
components
in
a
simple
manner.
Code
is
used,
no
input
no
documentation.
Executed
to
make
sure
that
the
component
is
compiled
and
run.
20.
What
is
functional
system
testing?
Answer:
Testing
the
end
to
end
functionality
of
the
system
as
a
whole
is
defined
as
a
functional
system
testing.
21.
In
a
reactive
approach
to
testing,
when
would
you
expect
the
bulk
of
the
testing
to
begin?
Answer:
After
the
software
has
been
produced.
22.
What
are
the
different
methodologies
in
Agile
development
Model
?
Answer:
prototyping,
Rational
Unified
Model,
Rapid
Application
Development,
Extreme
programming
,
Scrum,
Agile,
Unified
Model,
Crystal,
23.
Which
activity
in
fundamental
test
process
include
evaluation
of
testability
of
the
function
and
system
requirements
?
Answer:
test
analysis
and
design.
24.
What
is
the
most
important
reason
to
use
risk
based
testing
?
Answer:
because
exhaustive
testing
is
impossible.
25.
What
is
random/monkey
testing?
When
it
is
used?
Answer:
Random
testing
often
known
as
monkey
testing.
In
such
type
of
testing
data
is
generated
randomly
often
using
a
tool
or
automated
mechanism.
With
this
randomly
generated
input
the
system
is
tested
and
results
are
analyzed
accordingly.
.
26.
Which
of
the
following
are
valid
objectives
for
incident
reports?
1. Provide
developers
and
other
parties
with
feedback
about
the
problem
to
enable
identification,
isolation
and
correction
as
necessary.
2. Provide
ideas
for
test
process
improvement.
3. Provide
testers
with
a
means
of
tracking
the
quality
of
the
system
under
test.
27.
Consider
the
following
techniques.
Which
are
static
and
which
are
dynamic
techniques?
1. Equivalence
Partitioning.
2. Use
Case
Testing.
3. Data
Flow
Analysis.
4. Exploratory
Testing.
5. Decision
Testing.
6. Inspections.
Answer:
Data
Flow
Analysis
and
Inspections
are
static;
Equivalence
Partitioning,
Use
Case
Testing,
Exploratory
Testing
and
Decision
Testing
are
dynamic
28.Why
are
static
testing
and
dynamic
testing
described
as
complementary?
Answer:
Because
they
share
the
aim
of
identifying
defects
but
differ
in
the
types
of
defect
they
find.
29.
What
are
the
phases
of
formal
review?
Answer:
planning,
kick-off,
individual
preparation,
review
meeting,
rework,
follow
up.
30.
What
are
the
roles
of
a
moderator?
Answer:
sometimes
known
as
the
review
leader,
leads
the
review
of
the
document,
including
planning,
kick-off
and
follow
up
,
mediates
between
various
points
of
view
and
decides
when
to
release
the
updated
document.
31.
What
is
an
equivalent
partitioning?
Answer:
choosing
a
single
input/output
value,
which
is
a
representative
of
a
group
of
input/output
values
for
all
valid
and
invalid
input/outputs.
32.
When
should
configuration
management
procedure
be
implemented?
Answer:
during
test
planning.
33.
A
type
of
functional
testing,
which
investigates
the
detection
of
threads
of
virus
attack.
Answer:
Security
testing.
34.
Testing
where
in
we
subject
the
target
of
the
test
,
to
varying
workloads
to
measure
and
evaluate
the
performance
behaviors
and
ability
of
the
target
and
of
the
test
to
continue
to
function
properly
under
these
different
workloads?
Answer:
Load
testing.
35.
Testing
activity
which
is
performed
to
expose
defects
in
the
interfaces
and
in
the
interaction
between
integrated
components
is
Answer:
integration
testing.
36.
When
regression
testing
should
be
performed?
Answer:
After
the
software
has
changed
or
when
the
environment
has
changed.
37.
What
is
negative
and
positive
testing?
Answer:
A
negative
test
is
when
you
put
in
an
invalid
input
and
receives
errors.
While
a
positive
testing,
is
when
you
put
in
a
valid
input
and
expect
some
action
to
be
completed
in
accordance
with
the
specification.
38.
What
is
the
purpose
of
test
completion
criteria?
Answer:
to
know
when
to
stop
testing,
when
a
test
level
is
completed,
when
we
have
achieved
pre-determined
level
of
quality
of
the
product.
39.
what
can
static
analysis
not
find
?
Answer:
memory
leaks.
40.
what
is
the
difference
between
re-testing
and
regression
testing?
Answer:
re-testing
checks
that
the
original
fault
is
fixed.
Regression
testing
checks..
we
all
know
that
that
is.
41.
What
are
experience
based
testing?
Answer:
error
guessing
,
fault
attack,
exploratory
testing.
42.
what
type
of
review
requires
formal
entry
and
exit
criteria.
Answer:
formal
review
(
inspection
)
.
43.
Could
reviews
and
inspection
be
considered
part
of
testing?
Answer:
Yes,
both
constitute
static
testing.
44.
An
input
field
takes
the
year
of
birth
between
1900
and
2004
what
are
the
boundary
values
for
testing
this
field?
Answer:
1899,1900,2004,2005
45.
Which
of
the
following
tools
would
be
involved
in
the
automation
of
regression
test?
a.
Data
tester
b.
Boundary
tester
c.
Capture/Playback
d.
Output
comparator.
Answer:
Output
comparator
46.
To
test
a
function,
what
has
to
write
a
programmer,
which
calls
the
function
to
be
tested
and
passes
it
test
data.
Answer:
Driver
47.
What
is
the
one
key
reason
developers
have
trouble
testing
their
own
product?
Answer:
lack
of
objective.
48.
How
much
testing
is
enough?
Answer:
depends
on
the
risk
for
the
industry,
contracts
and
regulations,
product
risk.
49.
When
should
testing
should
stop?
Answer:
when
exit
criteria
is
met:
deadline,
cost,
all
high
risk
testing
is
done,
no
serious
defects
are
left
out.
A
certain
percentage
is
met
50.
Which
of
the
following
is
the
main
purpose
of
the
integration
strategy
for
integration
testing
in
the
small?
Answer:
The
main
purpose
of
the
integration
strategy
is
to
specify
which
modules
to
combine,
when
and
how
many
at
once.
51.
what
is
semi-random
test
cases
?
Answer:
when
you
do
random
test
cases
and
put
equivalence
partitioning
to
get
rid
of
some
test
cases,
you
get
semi-random
test
cases.
52.
Given
the
following
code,
which
statement
is
true
about
the
minimum
number
of
test
cases
required
for
full
statement
and
branch
coverage?
Read
p
Read
q
IF
p+q>
100
THEN
Print
"Large"
ENDIF
IF
p
>
50
THEN
Print
"p
Large"
ENDIF
Answer:
1
statement
coverage,
2
for
branch
coverage.
53.
what
is
black
box
testing?
What
are
the
different
black
box
testing
technique?
Answer:
black
box
testing
uses
the
functional
specification
to
device
test
cases.
Equivalence
partitioning,
boundary
value
analysis,
decision
table
testing,
state
transition
testing,
use
case
testing
are
all
black
box
testing.
54.
Which
review
is
normally
used
to
evaluate
a
product
to
determine
its
suitability
for
intended
use
and
to
identify
discrepancies?
Answer:
Technical
Review
58.
Faults
found
should
originally
be
documented
by
whom?
Answer:
tester.
59.
Which
of
the
following
is
the
review
participant
who
has
created
the
item
to
be
reviewed?
Answer:
Author
60.
Why
boundary
value
analysis
provide
good
test
cases?
Answer:
because
most
of
the
defects
are
created
on
the
edges.
61.
What
makes
an
inspection
different
than
other
review
process?
Answer:
led
by
a
trained
moderator,
uses
formal
entry
and
exit
criteria,
used
formal
follow
up
process.
Based
on
rules
and
checklist.
62.
Why
can
be
tester
dependent
on
configuration
management?
Answer:
Because
configuration
management
assures
that
we
know
the
exact
version
of
the
testware
and
the
test
object
63.
What
is
a
V-model
?
Answer
:
a
software
development
model
that
should
how
testing
activities
integrates
with
development
phases.
64.
What
triggers
maintenance
testing?
Answer:
modification,
migration
and
retirement.
65.
What
is
test
coverage?
Answer:
Test
coverage
measures
in
some
specific
way
the
amount
of
testing
performed
by
a
set
of
tests
(derived
in
some
other
way,
e.g.
using
specification-
based
techniques).
66.
Why
is
incremental
integration
preferred
over
"big
bang"
integration?
Answer:
Because
incremental
integration
has
better
early
defects
screening
and
isolation
ability
67.
When
do
we
prepare
requirements
tractability
metrx
?
after/before
test
case
development
?
Answer:
you
prepare
RTM
before
you
develop
test
cases.
If
you
are
reviewing
the
requirements,
the
traceability
should
already
been
established.
If
you
are
following
a
sequential
development
methodology,
requirements
should
already
been
traceable
through
tools.
68.
what
is
the
process
that
starts
from
the
terminal
modules
?
Answer:
bottom
up
integration.
69.
During
which
test
activity
can
faults
be
found
most
effectively?
Answer:
during
test
planning.
70.
The
purpose
of
requirements
phase
is?
Answer:
to
freeze
requirements,
to
understand
user
needs
and
to
know
the
scope
of
testing.
71.
why
split
testing
into
different
stages
?
Answer:
Each
test
stage
has
a
different
purpose
It
is
easier
to
manage
testing
in
stages
We
can
run
different
test
into
different
environments
Performance
and
quality
of
the
testing
is
improved
using
phased
testing
72.
What
is
defect
remove
efficiency?
Answer:
DRE=Number
of
bugs
while
testing
/
number
of
bugs
while
testing
+
number
of
bugs
found
by
user
73.
Which
of
the
following
is
likely
to
benefit
most
from
the
use
of
test
tools
providing
test
capture
and
replay
facilities?
a)
Regression
testing
b)
Integration
testing
c)
System
testing
d)
User
acceptance
testing
Answer:
Regression
74.
how
would
you
estimate
the
amount
of
re-testing?
Answer:
from
previous
similar
projects
and
discussion
with
the
development
team.
75.
what
is
data
flow
analysis?
Answer:
the
use
of
date
through
the
code
76.
What
is
a
failure
?
Answer:
failure
is
a
departure
from
specified
behavior
77.
what
is
a
test
comparator
?
Answer:
an
automated
too
to
compare
results
of
different
tests.
78.
Who
is
responsible
to
document
all
the
issues,
points,
problems
that
were
identified
during
review
meeting?
Answer:
scribe.
79.
What
is
the
main
purpose
of
informal
review?
Answer:
to
get
some
benefit
in
an
inexpensive
way.
80.
What
is
the
purpose
of
test
design
technique?
Answer:
identify
test
conditions
and
test
cases.
81.
When
testing
a
grade
calculation
system,
a
tester
determines
that
all
scores
from
90
to
100
will
yield
a
grade
of
A,
but
scores
below
90
will
not.
This
analysis
is
known
as:
Answer:
Equivalence
partitioning
82.
A
test
manager
wants
to
use
the
resources
available
for
the
automated
testing
of
a
web
application.
The
best
choice
is
Answer:
dba,
web
specialist,
tester,
test
automator.
83.
During
the
testing
of
a
module
tester
'X'
finds
a
bug
and
assigned
it
to
developer.
But
developer
rejects
the
same,
saying
that
it's
not
a
bug.
What
'X'
should
do?
Answer:
Send
to
the
detailed
information
of
the
bug
encountered
and
check
the
reproducibility
84.
A
type
of
integration
testing
in
which
software
elements,
hardware
elements,
or
both
are
combined
all
at
once
into
a
component
or
an
overall
system,
rather
than
in
stages.
Answer:
Big-Bang
Testing
85.
In
practice,
which
Life
Cycle
model
may
have
more,
fewer
or
different
levels
of
development
and
testing,
depending
on
the
project
and
the
software
product.
For
example,
there
may
be
component
integration
testing
after
component
testing,
and
system
integration
testing
after
system
testing
Answer:
V-model
86.
Which
technique
can
be
used
to
achieve
input
and
output
coverage?
It
can
be
applied
to
human
input,
input
via
interfaces
to
a
system,
or
interface
parameters
in
integration
testing
Answer:
Equivalence
partitioning.
87.
"This
life
cycle
model
is
basically
driven
by
schedule
and
budget
risks"
This
statement
is
best
suited
for
Answer:
V-model.
88.
In
which
order
should
tests
be
run?
Answer:
The
most
important
one
must
tests
first
92.
The
later
in
the
development
life
cycle
a
fault
is
discovered,
the
more
expensive
it
is
to
fix.
Why?
Answer:
The
fault
has
been
built
into
more
documentation,
code,
tests,
etc
cost
escalation
model
and
error
of
propagation.
93.
What
is
Coverage
measurement?
Answer:
It
is
a
partial
measure
of
test
thoroughness.
94.
What
is
Boundary
value
testing?
Test
boundary
conditions
on,
below
and
above
the
edges
of
input
and
output
equivalence
classes.
For
instance,
let
say
a
bank
application
where
you
can
withdraw
maximum
Rs.20,000
and
a
minimum
of
Rs.100,
so
in
boundary
value
testing
we
test
only
the
exact
boundaries,
rather
than
hitting
in
the
middle.
That
means
we
test
above
the
maximum
limit
and
below
the
minimum
limit.
95.
What
is
Fault
Masking?
Answer:
Error
condition
hiding
another
error
condition.
96.
What
does
COTS
represent?
Answer:
Commercial
off
The
Shelf.
97.The
purpose
of
which
is
allow
specific
tests
to
be
carried
out
on
a
system
or
network
that
resembles
as
closely
as
possible
the
environment
where
the
item
under
test
will
be
used
upon
release?
Answer:
Test
Environment
98.
What
can
be
thought
of
as
being
based
on
the
project
plan,
but
with
greater
amounts
of
detail?
Answer:
Phase
Test
Plan
(goal
goal)
99.
What
is
exploratory
testing?
Exploratory
testing
is
a
hands-on
approach
in
which
testers
are
involved
in
minimum
planning
and
maximum
test
execution.
The
planning
involves
the
creation
of
a
test
charter,
a
short
declaration
of
the
scope
of
a
short
(1
to
2
hour)
time-boxed
test
effort,
the
objectives
and
possible
approaches
to
be
used.
As
the
tester
starts
exploring
the
system,
new
test
design
ideas
are
thought
of
on
the
fly
and
executed
against
the
software
under
test.
The
test
design
and
test
execution
activities
are
performed
in
parallel
typically
without
formally
documenting
the
test
conditions,
test
cases
or
test
scripts.
This
does
not
mean
that
other,
more
formal
testing
techniques
will
not
be
used.
For
example,
the
tester
may
decide
to
use
boundary
value
analysis
but
will
think
through
and
test
the
most
important
boundary
values
without
necessarily
writing
them
down.
Some
notes
will
be
written
during
the
exploratory-testing
session,
so
that
a
report
can
be
produced
afterwards.
100.
What
is
"use
case
testing"?
A
use
case
is
a
description
of
a
particular
use
of
the
system
by
an
actor
or
user.
It
is
used
widely
in
developing
tests
at
system
or
acceptance
level.
In
a
use-case,
an
actor
is
represented
by
"A"
and
system
by
"S".
First,
we
list
the
Main
Success
Scenario.
Exercise
the
whole
system
transaction
to
transaction
basis.
101.
What
is
the
difference
between
STLC
(Software
Testing
Life
Cycle)
and
SDLC
(Software
Development
Life
Cycle)
?
Answer:
SDLC
deals
with
development/coding
of
the
software
while
STLC
deals
with
validation
and
verification
of
the
software
102.
What
is
traceability
matrix?
Answer:
The
relationship
between
test
cases
and
requirements
is
shown
with
the
help
of
a
document.
This
document
is
known
as
traceability
matrix.
103.
What
is
Equivalence
partitioning
testing?
Answer:
Equivalence
partitioning
testing
is
a
software
testing
technique
which
divides
the
application
input
test
data
into
each
partition
at
least
one
of
equivalent
data
from
which
test
cases
can
be
derived.
By
this
testing
method
it
reduces
the
time
required
for
software
testing.
104.
What
is
white
box
testing
and
list
the
types
of
white
box
testing?
White
box
testing
technique
involves
selection
of
test
cases
based
on
an
analysis
of
the
internal
structure
(Code
coverage,
branches
coverage,
paths
coverage,
condition
coverage
etc.)
of
a
component
or
system.
It
is
also
known
as
Code-Based
testing
or
Structural
testing.
105.
In
white
box
testing
what
do
you
verify?
Answer:
In
white
box
testing
following
steps
are
verified.
1. Verify
the
security
holes
in
the
code
2. Verify
the
incomplete
or
broken
paths
in
the
code
3. Verify
the
flow
of
structure
according
to
the
document
specification
4. Verify
the
expected
outputs
5. Verify
all
conditional
loops
in
the
code
to
check
the
complete
functionality
of
the
application
6. Verify
the
line
by
line
coding
and
cover
100%
testing
106.
What
is
the
difference
between
static
and
dynamic
testing?
Answer:
Static
testing:
During
Static
testing
method,
the
code
is
not
executed
and
it
is
performed
using
the
software
documentation.
Dynamic
testing:
To
perform
this
testing
the
code
is
required
to
be
in
an
executable
form.
107.
What
is
verification
and
validation?
Answer:
Verification
is
a
process
of
evaluating
software
at
development
phase
and
to
decide
whether
the
product
of
a
given
application
satisfies
the
specified
requirements.
Validation
is
the
process
of
evaluating
software
at
the
end
of
the
development
process
and
to
check
whether
it
meets
the
customer
requirements.
108.
What
are
different
test
levels?
Answer:
There
are
four
test
levels
1. Unit/component/program/module
testing
2. Integration
testing
3. System
testing
4. Acceptance
testing
109.
What
is
Integration
testing?
Answer:
Integration
testing
is
a
level
of
software
testing
process,
where
individual
units
of
an
application
are
combined
and
tested.
It
is
usually
performed
after
unit
and
functional
testing.
110.
What
are
the
tables
in
test
plans?
Answer:
Test
design,
scope,
test
strategies,
approach
are
various
details
that
Test
plan
document
consists
of.
(SPACE
DIRT)
111.
What
is
the
difference
between
UAT
(User
Acceptance
Testing)
and
System
testing?
Answer:
System
Testing:
System
testing
is
finding
defects
when
the
system
under
goes
testing
as
a
whole,
it
is
also
known
as
end
to
end
testing.
In
such
type
of
testing,
the
application
undergoes
from
beginning
till
the
end.
UAT:
User
Acceptance
Testing
(UAT)
involves
running
a
product
through
a
series
of
specific
tests
which
determines
whether
the
product
will
meet
the
needs
of
its
users.
112.
Mention
the
difference
between
Data
Driven
Testing
and
Retesting?
Answer:
Retesting:
It
is
a
process
of
checking
bugs
that
are
actioned
by
development
team
to
verify
that
they
are
actually
fixed.
Data
Driven
Testing
(DDT):
In
data
driven
testing
process,
application
is
tested
with
multiple
test
data.
Application
is
tested
with
different
set
of
values.
113.
What
are
the
valuable
steps
to
resolve
issues
while
testing?
Answer:
Record
:
Log
and
handle
any
problems
which
has
happened
Report:
Report
the
issues
to
higher
level
manager
Control:
Define
the
issue
management
process
114.
What
is
the
difference
between
test
scenarios,
test
cases
and
test
script?
Difference
between
test
scenarios
and
test
cases
is
that
Test
Scenarios(Test
Plan)
:
Test
scenario
is
prepared
before
the
actual
testing
starts,
it
includes
plans
for
testing
product,
number
of
team
members,
environmental
condition,
making
test
cases,
making
test
plans
and
all
the
features
that
are
to
be
tested
for
the
product.
Test
Cases:
It
is
a
document
that
contains
the
steps
that
has
to
be
executed,
it
has
been
planned
earlier.
Test
Script:
It
is
written
in
a
programming
language
and
it's
a
short
program
used
to
test
part
of
functionality
of
the
software
system.
In
other
words
a
written
set
of
steps
that
should
be
performed
manually.
115.
What
is
Latent
defect?
Answer:
Latent
defect:
This
defect
is
an
existing
defect
in
the
system
which
does
not
cause
any
failure
as
the
exact
set
of
conditions
has
never
been
met
116.
What
are
the
two
parameters
which
can
be
useful
to
know
the
quality
of
test
execution?
Answer:
Defect
reject
ratio
defects
that
did
not
have
an
impact
Defect
leakage
ratio
defects
not
found
by
testers.
117.
What
is
the
function
of
software
testing
tool
"phantom"?
Answer:
Phantom
is
a
freeware,
and
is
used
for
windows
GUI
automation
scripting
language
118.
Explain
what
is
Test
Deliverables?
Answer:
Test
Deliverables
are
set
of
documents,
tools
and
other
components
that
has
to
be
developed
and
maintained
in
support
of
testing.
There
are
different
test
deliverables
at
every
phase
of
the
software
development
lifecycle
Before
Testing
During
Testing
After
the
Testing
119.
What
is
mutation
testing?
Answer:
Testing
of
test
cases
basically.
Mutation
testing
is
a
technique
to
identify
if
a
set
of
test
data
or
test
case
is
useful
by
intentionally
introducing
various
code
changes
(bugs)
and
retesting
with
original
test
data/
cases
to
determine
if
the
bugs
are
detected.
To
check
the
usability
of
test
cases.
120.
What
all
things
you
should
consider
before
selecting
automation
tools
for
the
AUT?
Answer:
maturity
of
testing
process
within
the
organization,
cost,
alternative
approaches,
vendor
service,
pilot
project,
changes
needed
in
the
testing
process
or
in
the
tool,
long
term
benefit
.
121.
How
will
you
conduct
Risk
Analysis?
Answer:
For
the
risk
analysis
following
steps
need
to
be
implemented:
a)
Finding
the
score
of
the
risk
b)
Making
a
profile
for
the
risk
c)
Changing
the
risk
properties
d)
Deploy
the
resources
of
that
test
risk
e)
Making
a
database
of
risk
122.
What
are
the
categories
of
debugging?
Answer:
Categories
for
debugging
a)
Brute
force
debugging
most
common,
least
effective,
desk
checking
using
a
debugger
to
step
through.
b)
Backtracking
effective
for
small
programs/modules,
desk
checking
in
reverse.
c)
Cause
elimination
induction/deduction
+
binary
partitioning.
d)
Program
slicing
-
my
method,
commenting
portion
of
the
code.
e)
Fault
tree
analysis
top
down
deductive
approach,
combination
of
different
scenarios
that
could
cause
the
system
to
fail,
uses
logic
gates
symbol,
123.
What
is
fault
masking
explain
with
example?
When
presence
of
one
defect
hides
the
presence
of
another
defect
in
the
system
is
known
as
fault
masking.
Example
:
If
the
"Negative
Value"
cause
a
firing
of
unhandled
system
exception,
the
developer
will
prevent
the
negative
values
input.
This
will
resolve
the
issue
and
hide
the
defect
of
unhandled
exception
firing.
124.
Explain
what
is
Test
Plan?
What
are
the
information
that
should
be
covered
in
Test
Plan?
A
test
plan
can
be
defined
as
a
document
describing
the
scope,
approach,
resources
and
schedule
of
testing
activities
and
a
test
plan
should
cover
the
following
details.
Test
Strategy
Test
Objective
Exit/Suspension
Criteria
Resource
Planning
Test
Deliverables
125.
How
you
can
eliminate
the
product
risk
in
your
project?
Answer:
eliminate
ambiguity
in
the
requirements,
static
review,
test
For
non-functional
requirements,
and
functional
requirements,
conformance
with
the
user.
126.
What
are
the
common
risk
that
leads
to
the
project
failure?
Answer:
supplier
issues,
contractual
obligation,
skills
and
personal
issues,
Lack
of
appreciation
for
testing,
technical
or
specialist
issues.
127.
On
what
basis
you
can
arrive
to
an
estimation
for
your
project?
Answer:
Metrics
based
approach
and
expert
based
approach,
analytical,
methodical,
contractual
or
regulatory,
consultative,
regression
aversion,
128.
Explain
how
you
would
allocate
task
to
team
members
?
Task
Member
Analyze
software
requirement
All
the
members
specification
Create
the
test
specification
Tester/Test
Analyst
Build
up
the
test
environment
Test
administrator
Execute
the
test
cases
Tester
Report
defects
Tester
129.
Explain
what
is
testing
type
and
what
are
the
commonly
used
testing
type?
Answer:
functional
testing,
non-functional
testing,
structural
testing,
confirmation
testing,
regression
testing,
maintenance
testing.
130.
While
monitoring
your
project
what
all
things
you
have
to
consider?
The
things
that
has
to
be
taken
in
considerations
are
Is
you
project
on
schedule
Are
you
over
budget
Are
you
working
towards
the
same
career
goal
Have
you
got
enough
resources
Are
there
any
warning
signs
of
impending
problems
Is
there
any
pressure
from
management
to
complete
the
project
sooner
131.
What
are
the
common
mistakes
which
creates
issues?
Answer:
convey
testing
results
without
hurting
personal
feelings,
testers
lack
of
objective,
use
test
results
to
judge
team
members,
team
members
technical
ability
and
skill,
lack
of
appreciation
for
testing,
different
view
during
inspection.
132.
What
does
a
typical
test
report
contains?
What
are
the
benefits
of
test
reports?
Answer:
test
Identification
number,
summary,
Summary
of
test
activities,
Evaluation,
variance,
comprehensive
assessment,
approvals.
an
assessment
of
defect
remaining,
economic
benefit
of
continuing
testing,
outstanding
risk,
level
of
confidence
in
tested
software.
The
benefits
of
test
reports
are:
Whether
the
goal
was
correctly
set,
Whether
the
testing
strategy
taken
was
adequate.
Whether
the
testing
was
effective
of
meeting
the
testing
goal.
133.
What
is
test
management
review
and
why
it
is
important?
Answer:
Management
review
is
also
referred
as
Software
Quality
Assurance
or
SQA.
SQA
focuses
more
on
the
software
process
rather
than
the
software
work
products.
It
is
a
set
of
activities
designed
to
make
sure
that
the
project
manager
follows
the
standard
process.
SQA
helps
test
manager
to
benchmark
the
project
against
the
set
standards.
-Verification
134.
What
are
the
best
practices
for
software
quality
assurance?
Answer:
The
best
practices
for
an
effective
SQA
implementation
is
Continuous
Improvement
Documentation
Tool
Usage
Metrics
Responsibility
by
team
members
Experienced
SQA
auditors
136.
What
is
difference
between
Test
matrix
and
Traceability
matrix?
Answer:
Test
Matrix:
Test
matrix
is
used
to
capture
actual
quality,
effort,
the
plan,
resources
and
time
required
to
capture
all
phases
of
software
testing
Traceability
Matrix:
Mapping
between
test
cases
and
customer
requirements
is
known
as
Traceability
Matrix
137.
In
manual
testing
what
are
stubs
and
drivers?
Answer:
Both
stubs
and
drivers
are
part
of
incremental
testing.
In
incremental
testing
there
are
two
approaches
namely
bottom
up
and
top
down
approach.
Drivers
are
used
in
bottom
up
testing
and
stub
is
used
for
top
down
approach.
In
order
to
test
the
main
module,
stub
is
used,
which
is
a
dummy
code
or
program
.
138.
What
are
the
step
you
would
follow
once
you
find
the
defect?
Once
defect
is
found
you
would
follow
the
step
Answer:
a)
Recreate
the
defect
b)
Attach
the
screen
shot
c)
Log
the
defect
139.
Explain
what
is
"Test
Plan
Driven"
or
"Key
Word
Driven"
method
of
testing?
This
technique
uses
the
actual
test
case
document
developed
by
testers
using
a
spread
sheet
containing
special
"key
Words".
The
key
words
control
the
processing.
140.
What
is
DFD
(Data
Flow
Diagram)?
Answer:
graphical
representation
of
flow
of
data
through
the
system.
141.
Explain
what
is
LCSAJ?
Answer:
LCSAJ
stands
for
'linear
code
sequence
and
jump'.
It
consists
of
the
following
three
items
a)
Start
of
the
linear
sequence
of
executable
statements
b)
End
of
the
linear
sequence
c)
The
target
line
to
which
control
flow
is
transferred
at
the
end
of
the
linear
sequence
used
to
identify
code
coverage,
100%
LCSAJ
=
100%
SCV,100%
BCV,
100%
procedure/functional
call
coverage,
100%
multiple
condition
coverage.
Its
primary
use
with
dynamic
software
analysis
is
to
answer,
how
much
testing
is
enough?
142.
Explain
what
is
N+1
testing?
Answer:
The
variation
of
regression
testing
is
represented
as
N+1.
In
this
technique
the
testing
is
performed
in
multiple
cycles
in
which
errors
found
in
test
cycle
'N'
are
resolved
and
re-tested
in
test
cycle
N+1.
The
cycle
is
repeated
unless
there
are
no
errors
found.
143.
What
is
Fuzz
testing
and
when
it
is
used?
Answer:
Fuzz
testing
is
used
to
detect
security
loopholes
and
coding
errors
in
software.
In
this
technique
random
data
is
added
to
the
system
in
attempt
to
crash
the
system.
If
vulnerability
persists,
a
tool
called
fuzz
tester
is
used
to
determine
potential
causes.
This
technique
is
more
useful
for
bigger
projects
but
only
detects
major
fault.
144.
Mention
what
are
the
main
advantages
of
statement
coverage
metric
of
software
testing?
The
benefit
of
statement
coverage
metric
is
that
a)
It
does
not
require
processing
source
code
and
can
be
applied
directly
to
object
code
b)
Bugs
are
distributed
evenly
through
code,
due
to
which
percentage
of
executable
statements
covered
reflects
the
percentage
of
faults
discovered.
mante
parlam
na.
145.
How
to
generate
test
cases
for
replace
string
method?
a)
If
characters
in
new
string
>
characters
in
previous
string.
None
of
the
characters
should
get
truncated
b)
If
characters
in
new
string<
characters
in
previous
string.
Junk
characters
should
not
be
added
c)
Spaces
after
and
before
the
string
should
not
be
deleted
d)
String
should
be
replaced
only
for
the
first
occurrence
of
the
string
146.
How
will
you
handle
a
conflict
amongst
your
team
members?
Answer:
convey
test
result
in
a
non-personal
manner
and
bugs
founds
are
welcomed
as
a
mean
to
improve
the
quality
of
the
product.
Remind
every
one
that
our
goal
is
to
enhance
quality,
not
find
faults
of
members.
Bugs
found
should
be
welcomed.
147.
Mention
what
are
the
categories
of
defects?
Mainly
there
are
three
defect
categories
Wrong:
When
requirement
is
implemented
incorrectly
Missing:
It
is
a
variance
from
the
specification,
an
indication
that
a
specification
was
not
implemented
or
a
requirement
of
the
customer
is
not
met
Extra:
A
requirement
incorporated
into
the
product
that
was
not
given
by
the
end
customer.
It
is
considered
as
a
defect
because
it
is
a
variance
from
the
existing
requirements
148.
Explain
how
does
a
test
coverage
tool
works?
The
code
coverage
testing
tool
runs
parallel
while
performing
testing
on
the
actual
product.
The
code
coverage
tool
monitors
the
executed
statements
of
the
source
code.
When
the
final
testing
is
done
we
get
a
complete
report
of
the
pending
statements
and
also
get
the
coverage
percentage.
149.
Mention
what
is
the
difference
between
a
"defect"
and
a
"failure"
in
software
testing?
Error/mistake
->
defect/bug/fault->failure.
150.
Explain
how
to
test
documents
in
a
project
that
span
across
the
software
development
lifecycle?
Test
plan
for
all
the
levels
in
V-Model
basically.
Central/Project
test
plan:
It
is
the
main
test
plan
that
outlines
the
complete
test
strategy
of
the
project.
This
plan
is
used
till
the
end
of
the
software
development
lifecycle
Acceptance
test
plan:
This
document
begins
during
the
requirement
phase
and
is
completed
at
final
delivery
System
test
plan:
This
plan
starts
during
the
design
plan
and
proceeds
until
the
end
of
the
project
Integration
and
Unit
test
plan:
Both
these
test
plans
start
during
the
execution
phase
and
last
until
the
final
delivery
151.
Explain
which
test
cases
are
written
first
black
boxes
or
white
boxes?
Black
box
test
cases
are
written
first
as
to
write
black
box
test
cases;
it
requires
project
plan
and
requirement
document
all
these
documents
are
easily
available
at
the
beginning
of
the
project.
While
writing
white
box
test
cases
requires
more
architectural
understanding
and
is
not
available
at
the
start
of
the
project.
152.
Explain
what
is
the
difference
between
latent
and
masked
defects?
Latent
defect:
A
latent
defect
is
an
existing
defect
that
has
not
caused
a
failure
because
the
sets
of
conditions
were
never
met
Masked
defect:
It
is
an
existing
defect
that
has
not
caused
a
failure
because
another
defect
has
prevented
that
part
of
the
code
from
being
executed
153.
Mention
what
is
bottom
up
testing?
Answer:
one
of
the
strategies
in
integration
testing,
drivers
are
used.
154.
Mention
what
are
the
different
types
of
test
coverage
techniques?
Different
types
of
test
coverage
techniques
include
Statement
Coverage:
It
verifies
that
each
line
of
source
code
has
been
executed
and
tested
Decision
Coverage:
It
ensures
that
every
decision
in
the
source
code
is
executed
and
tested
Path
Coverage:
It
ensures
that
every
possible
route
through
a
given
part
of
code
is
executed
and
tested
Condition
coverage:
All
the
conditions
in
a
decision
are
covered.
155.
Mention
what
is
the
meaning
of
breadth
testing?
Answer:
Breadth
testing
is
a
test
suite
that
exercises
the
full
functionality
of
a
product
but
does
not
test
features
in
detail,
related
to
top
down
integration
testing.
156.
Mention
what
is
the
difference
between
Pilot
and
Beta
testing?
Answer:
The
difference
between
pilot
and
beta
testing
is
that
pilot
testing
is
actually
done
using
the
product
by
the
group
of
user
before
the
final
deployment
and
in
beta
testing
we
do
not
input
real
data,
but
it
is
installed
at
the
end
customer
to
validate
if
the
product
can
be
used
in
production.
a
pilot
usually
has
completed
its
quality
phases
and
is
ready
for
release
while
beta
testing
is
the
last
quality
phase
prior
to
release.
Beta
feedback
allows
you
to
make
changes
to
your
product
while
a
pilot
is
focused
on
your
process.
157.
Explain
what
is
the
meaning
of
Code
Walk
Through?
Answer:
Code
Walk
Through
is
the
informal
analysis
of
the
program
source
code
to
find
defects
and
verify
coding
techniques
158.
Mention
what
are
the
basic
components
of
defect
report
format?
The
basic
components
of
defect
report
format
includes
Answer:
CRUD
GAS
DISC
SSD.
159.
Mention
what
is
the
purpose
behind
doing
end-to-end
testing?
End-to
end
testing
is
done
after
functional
testing.
The
purpose
behind
doing
end-
to-end
testing
is
that
To
validate
the
software
requirements
and
integration
with
external
interfaces
Testing
application
in
real
world
environment
scenario
Testing
of
interaction
between
application
and
database
160.
Explain
what
it
means
by
test
harness?
A
test
harness
is
configuring
a
set
of
tools
and
test
data
to
test
an
application
in
various
conditions.
It
involves
monitoring
the
output
with
expected
output
for
correctness.
161.
Explain
in
a
testing
project
what
testing
activities
would
you
automate?
In
a
testing
project
testing
activities
you
would
automate
are
Tests
that
need
to
be
run
for
every
build
of
the
application.
E.g.
regression
test,
test
with
high
impact
that
must
be
tested
(also
falls
under
regression),
mission
critical
tests.
Tests
that
use
multiple
data
for
the
same
set
of
actions
Identical
tests
that
needs
to
be
executed
using
different
browsers
Transaction
with
pages
that
do
not
change
in
short
time
Test
that
saves
time
if
automated.
How
complex
it
is
to
automate
the
test
and
what
are
the
chances
of
it
producing
false
result.
162.
What
is
grey
box
testing?
Answer:
it
is
a
combination
of
white
box
and
black
box
testing.
In
this,
we
first
look
at
the
code
and
the
structure
of
the
software
to
have
a
better
understanding
of
how
the
software
is
constructed.
And
then
we
move
on
to
develop
test
cases
in
black
box
testing.
White
box
->
black
box.
163.
what
is
usability
testing
?
Answer:
Usability
testing
is
a
testing
methodology
where
the
end
customer
is
asked
to
use
the
software
to
see
if
the
product
is
easy
to
use,
to
see
the
customer's
perception
and
task
time
164.
what
are
the
cateogies
of
defect
?
Answer:
wrong,
missing,
extra.
165.
How
do
you
define
a
testing
policy?
The
following
are
the
important
steps
used
to
define
a
testing
policy
in
general.
But
it
can
change
according
to
your
organization.
Let's
discuss
in
detail
the
steps
of
implementing
a
testing
policy
in
an
organization.
Definition:
The
first
step
any
organization
needs
to
do
is
define
one
unique
definition
for
testing
within
the
organization
so
that
everyone
is
of
the
same
mindset.
How
to
achieve:
How
are
we
going
to
achieve
our
objective?
Is
there
going
to
be
a
testing
committee,
will
there
be
compulsory
test
plans
which
need
to
be
executed,
etc?.
Evaluate:
After
testing
is
implemented
in
a
project
how
do
we
evaluate
it?
Are
we
going
to
derive
metrics
of
defects
per
phase,
per
programmer,
etc.
Finally,
it's
important
to
let
everyone
know
how
testing
has
added
value
to
the
project?.
Standards:
Finally,
what
are
the
standards
we
want
to
achieve
by
testing?
For
instance,
we
can
say
that
more
than
20
defects
per
KLOC
will
be
considered
below
standard
and
code
review
should
be
done
for
it.
166.
are
there
more
defects
in
design
phase
or
coding
phase
?
Answer:
The
design
phase
is
more
error
prone
than
the
execution
phase.
One
of
the
most
frequent
defects
which
occur
during
design
is
that
the
product
does
not
cover
the
complete
requirements
of
the
customer.
Second
is
wrong
or
bad
architecture
and
technical
decisions
make
the
next
phase,
execution,
more
prone
to
defects.
167.
what
are
different
types
of
verification
?
Answer:
informal,
walkthrough,
technical
review,
inspection.
168.
which
test
cases
are
written
first
?
white
or
black
?
Answer:
black
box
testing
is
written
first
because
the
requirements
specification
are
ready
before
the
code
and
design.
169.
what
is
a
test
log
?
Answer:
The
IEEE
Std.
829-1998
defines
a
test
log
as
a
chronological
record
of
relevant
details
about
the
execution
of
test
cases.
It's
a
detailed
view
of
activity
and
events
given
in
chronological
manner.
170.
What
kind
of
input
do
we
need
from
the
end
user
to
begin
proper
testing?
The
product
has
to
be
used
by
the
user.
He
is
the
most
important
person
as
he
has
more
interest
than
anyone
else
in
the
project.
From
the
user
we
need
the
following
data:
The
first
thing
we
need
is
the
acceptance
test
plan
from
the
end
user.
The
acceptance
test
defines
the
entire
test
which
the
product
has
to
pass
so
that
it
can
go
into
production.
We
also
need
the
requirement
document
from
the
customer.
The
customer
should
also
define
the
risky
and
priority.
The
customer
should
also
provide
proper
data
for
testing.
171.
Can
you
explain
the
workbench
concept?
A
workbench
is
referred
to
as
phases,
steps,
and
tasks
as
shown
in
the
following
figure.
There
are
five
tasks
for
every
workbench:
Input:
Every
task
needs
some
defined
input
and
entrance
criteria.
Execute:
transform
the
input
into
the
expected
output.
Check:
Check
steps
assure
that
the
output
after
execution
meets
the
desired
result.
Production
output:
If
the
check
is
right
the
production
output
forms
the
exit
criteria
of
the
workbench.
Rework:
During
the
check
step
if
the
output
is
not
as
desired
then
we
need
to
again
start
from
the
execute
step.
172.
What
is
defect
cascading?
Answer
Defect
cascading
is
a
defect,
which
is
caused
by
another
defect.
One
defect
triggers
the
other
defect.
Not
necessarily
error
of
propagation.
173.
What
are
different
strategies
of
roll
out?
Answer:
pilot
(user),
gradual
(software),
parallel,
phased(incremental)
installation.
174.
What
are
the
purposes
of
test
cases?
Answer:
to
identify
defects
and
to
reduce
test
cases.
175.
How
would
you
test
a
login
feature?
Sign
in
with
valid
login,
Close
browser
and
reopen
and
see
whether
you
are
still
logged
in
or
not.
Session
management
is
important
how
do
we
keep
track
of
logged
in
users,
is
it
via
cookies
or
web
sessions?
Sign
in,
then
logout
and
then
go
back
to
the
login
page
to
see
if
you
are
truly
logged
out.
Login,
then
go
back
to
the
same
page,
do
you
see
the
login
screen
again?
Sign
in
from
one
browser,
then
open
another
browser
to
see
if
you
need
to
sign
in
again?
Login,
change
password,
and
then
logout,
then
see
if
you
can
login
again
with
the
old
password
176.
What
is
Accessibility
Testing?
Answer:
Verifying
a
product
is
accessible
to
the
people
having
disabilities
(deaf,
blind,
mentally
disabled
etc.).
177.
What
is
Benchmark
Testing?
Answer:
a
kind
of
performance
testing.
Benchmarking
testing
is
the
process
of
comparing
application
performance
with
respect
to
industry
standard
given
by
some
other
organization.
It
is
a
standard
testing
which
specifies
where
our
application
stands
with
respect
to
others
178.
What
is
CMMI?
Answer:
The
Capability
Maturity
Model
for
Software
(CMM
or
SW-CMM)
is
a
model
for
judging
the
maturity
of
the
software
processes
of
an
organization
and
for
identifying
the
key
practices
that
are
required
to
increase
the
maturity
of
these
processes
179.
What
is
the
difference
between
interoperability
and
compatibility
testing
with
some
examples?
Answer:
Interoperability:-To
check
if
the
software
can
co
exist
with
other
supporting
softwares
in
the
system.
Compatibility:-To
check
if
the
software
runs
on
different
types
of
operating
systems
according
to
customer
requirements
180.
What
is
Scalability
Testing?
Answer:
Performance
testing
focused
on
ensuring
the
application
under
test
gracefully
handles
increases
in
workload.
181.
What
is
baseline
testing?
Answer:
Baseline
Testing
is
one
of
the
types
of
non-functional
testing.
It
refers
to
the
validation
of
documents
and
specifications
on
which
test
cases
would
be
designed.
It
is
the
baseline
requirements
against
which
you
compare
the
testing
progress
to
go
towards
benchmark
(for
example).
182.
What
is
Mutation
testing
&
when
can
it
be
done?
Mutation
testing
is
a
performed
to
find
out
the
defect
in
the
program.
It
is
performed
to
find
put
bugs
in
specific
module
or
component
of
the
application.
Mutation
testing
is
based
on
two
assumptions:
Competent
programmer
hypothesis:
according
this
hypothesis
we
suppose
that
program
write
the
correct
code
of
the
program.
Coupling
effect:
according
to
this
effect
collection
of
different
set
of
test
data
can
also
find
large
and
complex
bugs.
In
this
testing
we
insert
few
bugs
into
program
to
examine
the
optimal
test
inputs.
183.
What
is
the
purpose
of
test
strategy?
We
need
Test
Strategy
for
the
following
reasons:
1.
To
have
a
signed,
sealed,
and
delivered
document,
where
the
document
contains
details
about
the
testing
methodology,
test
plan,
and
test
cases.
2.
Test
strategy
document
tells
us
how
the
software
product
will
be
tested.
3.
Test
strategy
document
helps
to
review
the
test
plan
with
the
project
team
members.
4.
It
describes
the
roles,
responsibilities
and
the
resources
required
for
the
test
and
schedule.
5.
When
we
create
a
test
strategy
document,
we
have
to
put
into
writing
any
testing
issues
requiring
resolution.
The
test
strategy
is
decided
first,
before
lower
level
decisions
are
made
on
the
test
plan,
test
design,
and
other
testing
issues.
184.
What
are
the
types
of
maintenance?
There
are
four
types
of
maintenance.
They
are:
-
Corrective
Maintenance
Correcting
problems
that
arise
during
the
use
of
the
system.
-
Adaptive
Maintenance
-
Adaptations
to
address
requirements
that
crop
up
due
to
changes
in
the
environment
or
new
regulations.
-
Perfective
Maintenance
enhancement
to
improve
the
safety,
reliability,
efficiency
or
cost-effective
of
operation.
-
Preventive
Maintenance
changing
the
existing
system
so
as
to
reduce
the
risk
of
failure
while
operating.
185.
What
is
the
difference
between
bug
leakage
and
bug
release?
Answer:
when
customer
finds
a
bug
after
release
it
is
called
bug
leakage
and
when
a
software
is
handed
over
to
the
testing
team
with
a
known
bug,
it
is
called
bug
release
186.
Advantages
of
water
fall
model
?
Answer:
suitable
for
projects
where
quality
is
more
important
than
cost
and
time,
well
documented
and
every
phase
has
corresponding
work
product
to
review.
Traceability
is
better
than
incremental
approach,
187.
advantage
of
black-box
testing?
Answer:
can
be
developed
as
soon
as
requirements
are
ready,
dont
have
to
wait
for
the
code,
testers
may
not
need
technical
knowledge
about
the
code
to
develop
test
cases.
Directly
checks
the
software
against
the
requirements.
188.
Why
exploratory
testing
are
not
identical?
Answer:
On
an
exploratory
testing
session,
the
tester
executes
a
chain
of
actions
against
the
system,
each
action
depends
on
the
result
of
the
previous
action,
hence
the
outcome
of
the
result
of
the
actions
could
influence
what
the
tester
does
next;
therefore
the
test
sessions
are
not
identical.
189.
how
do
you
verify
the
result
of
your
search
on
search
page?
Answer:
there
are
two
ways
to
do
it
:
1)
know
the
source
of
data(xml,
database)
and
compare
2)
make
up
mock
data
and
check
against
it
.
190.
what
is
ad-hoc
testing?
Answer:
related
to
monkey
testing.
A
testing
phase
where
the
tester
tries
to
break
the
system
by
randomly
trying
the
systems
functionality
191.
What
criteria
do
you
consider
for
NOT
automating
the
test
?
Answer:
1)
Usability
testing
very
hard
to
automate
if
user
finds
it
friendly.
2)
Tests
need
to
be
executed
once
low
priority
tests,
adhoc.
3)
Test
without
predictable
results
4)
Dynamic
testing,
Security
testing,
Performance
testing.
5)
Tests
need
to
be
verified
visually.
6)
Tests
need
to
be
executed
quickly
making
automation
takes
time.
192.
what
are
the
pros
and
cons
of
automating
tests
at
UI
layer?
Answer:
Pros:
can
validate
user
journey
because
it
mimics
user
interaction,
can
be
shown
to
the
customer
what
tests
are
run(capture/play
back),
Cons:
can
be
very
brittle
(
can
break
because
UI
changes
but
functionality
did
not
change)
,
progress
is
slow
because
of
3rd
party
connection
and
response
from
the
system,
unrecognizable
objects
on
the
UI
,
because
it
is
slow
cannot
have
too
many
tests.
193.
Why
would
you
want
to
automate
a
Test?
Answer:
improve
quality
by
saving
time
to
do
test
design
and
exploratory
testing,
More
accurate
results
194.
What
is
smoke
testing?
Answer:
also
known
as
build
verification
testing,
smoke
testing
checks
if
the
most
important
function
works
and
the
build
is
stable
enough
for
further
testing.
It
helps
exposing
integration
and
major
problems
early
in
the
life-cycle.
Smoke
testing
should
be
automated
if
builds
are
prepared
frequently.
It
is
a
form
or
regression
testing
with
the
most
major
functionality
automated.
195.
What
are
the
benefits
of
smoke
testing?
Answer:
It
exposes
defects
early.
It
uncovers
integration
problems.
It
provides
some
level
of
confidence
to
go
forward
with
more
testing.
196.
What
documents
do
you
refer
when
you
create
test
cases?
Answer:
It
depends
on
what
level
the
test
case
is
used
for
and
what
kind
of
test
we
are
doing.
For
black
box
testing,
we
use
requirements
documentation
and
Use
cases,
for
white
box
testing
we
use
the
code
instead.
Refer
to
V-Model.
197.
How
would
you
create
test
cases
without
any
documentation?
Answer:
discussion
with
business
analyst,
developer
or
user.
198.
What
does
a
use
case
document
include?
Answer:
it
includes
cover
page,
revision
history,
flow
of
events
(alternative
flow
and
normal
flow),
exception,
special
requirements,
pre-condition,
post-condition.