Professional Documents
Culture Documents
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.