STE UT-2 QB

Explain the "Test Infrastructure" components.

Describe the test reporting in details.
How to prepare a surmmary report?
Prepare SIX test cases for sign-in form of gmail account.
What is test management?

What are the causes of defect?

Describe the techniques for finding defect.

Explain the defect template with its attributes.
Prepare the Defect Report for withdraw of Money from
ATM machine.

Prepare the Defect Report for any login form.

What is Manual testing ? Adv and Dis Adv of it.

How to select testing tools ? Explain in detail.
What is software testing automation? Adv and Dis Adv
of it.

Define metrics and measurements. Explain need of

software measurement.
1/8/2024,752 AM |8 | UNoategotzed

No
 Q. Explain the test infrastructure management with its
Components.
Ans- Testing requires a robust infrastructureto be planned upfront.
Ihis infrastructure is made up of three essential elements.

1) A test case database (TCDB): A test case database captures

all the relevant information about the test cases in an
organization.
Someof the entities and the attributes are given in following table
Sr. Test Case Purpose Attributes
No.
Test case ld
Records all static Test case name
Test case information about (File name)
tests. Test case oWner
Associated files
for test case.
Provide mappng Test case Id
Test casë between the tests and Module Id
product the corresponding
product features,
reference enables identification
of test cases for
given feature.
Gives the history of Test case Id
wien the test cASE Run date
WAS run and what Tine taken
Test cse
run bistory wIS tÉSlt ,provided
Inputs on selection of
Run
Status(Success/
test for regression
Failure)
Gives details of test Test caSe Jd
CASes introduced to Defeet
Test caae test certain specifc reference
defeet defects detected in
4
the product, pruvides
reference inputs on the
selection of test for
regressiön runs.
A test case database captures all the relevant information about
the test cases in an organization.
Some of the entities and attributes in each of the entities in such
a TCDB are:
Test case
+ Test case-product cross reference
t Test case run history
+ Test case- defect cross reference

2. Defect repository
It captures all the relevant information of defect repository for a product.
The information thatadefect repository includes
Defect details
* Defect test detail
+ Fix details
t Communication

3. Configuration Management (CM) repository andtool:

* Software Configuration Management is defined as a process to
systematically manage, organize, and control the changes in the
documents, codes, andother entities duringthe Software Development
Life Cycle.
* It keeps track of change control and version control of allthe
files/entities that make up a software product. Change control
ensures that

+ Changes to test files are made in a controlled fashion and

only with proper approvals.
+ Change are made by one test engineer are not accidently
lost or overwritten by other changes.
+ Each change produces distinct version of the file that is
re-creatable at any point of time.
* Everyone gets access to only the most recent version of
the test files.
 TCDB

Test c
Test case
Test CASA lect
produci XAEF
XREF
Test cas
in!o

SCH

Product Dçlect
test cases delails Dalect
Environ Producd Defect Conmuri
nenl fix delal cation
ile
Prodict Delac#
tafion de!ais

System
to b e
Testd

Test Te sting
Administrator, Platform

Connponént

Test
Testing
Tools LIbrary
Âutonate d
Testing
Praçtlces

Test Infrastructure

FOR SOME Questions Refer our Notebook Also.

 test manager andare kept in the documents

Q. Explain howsummary report is prepared in test planning.

Ans-Test summary report:
The final step in atest cycle is to recommendthe suitability of a product
for release. Areport that summarizes the result of a test cycle is the test
summary report.
There are two types of test summary report:
1.Phase wise test summary ,which is produced at the end of every
phase
2. Final test summary report.
ASummary report should present
1. Test Summary report ldentifier
2. Description ldentify the test items being
test id reported in this report with
3. Variances mention any deviation from test
any.
plans, test procedures, if
4. Summary of results all the results are
resolved incidents and their solutions. mentioned here with the
5. Comprehensive
assessment and recommendation for release should
Include Fit for release assessment and
recommendation of release
OR
The final step in a test cycle is to recommend the suitability of a
product for release.
Areport that summarizes the result of a test cycle is the test summary
report.
There are two types of test summary report:
Phasewise test summary, which is produced at the end of every
phase
Final test summary report.
ASummary report should present: Test Summary report ldentifier
Description ldentify the test items being reported in this report with test
id
1)Variances: Mention any deviation from test plans, test procedures, if
any.
2) Summary of results All the results are mentioned here with the
resolved incidents and their solutions.
3) Comprehensive assessment and
include Fit for release assessment andrecommendation for release should
recommendation of release.
Q. What are the contents of Test
Q.Give any two root causes of defects, Also give any two effects of defects of defects:
ANS:
i. Miscommunication of requirements introduces error in code.
ii. Lack of design Experience.
ii. Lack of coding practice.
iv, Unrealistic time schedule for development.
v. Multiple changes in the requirements.

Efects of defects
i. Adefect is an error in coding or logic that causes atrogra tÕ failor to produce
incorrect /unexpected results.
ii. It iscommonly refers to troubles with the softwaie produgts, with ts external
behavior or with its internal features.
i . Increased complexity of software.
iv. Programming Errors

ST-CH-4 [Make UR Own Style---9145069310]

 Defect Sever

finding defects? Explain in detail

Q. What are different techniques for
threeiçafegòries.
ANS:- Techniques to find defects into following
quality controjdefide checkingthe software
Static Techniques: Static techniques of
is a<[o termed desk
product and related artifacts without executing themn inapection,
checking/verification /white box testing'. It may includereyiews, walkthroughs,
the help of a checklist,
and audits. Here the work product is reviewed by the eyiewrwith locate the defect with
standards, any other artifact, knowledge and experiende inorderto involves
respect to the established criteria. Static technigue is s£ naned becase it
xecution of code, product, documentation, etc. This technique helps in establishing
Conformance to requiremenis view.

Dynamic Techniques: Dynamic testing is a validation technique which includes dummy

or actual execution of work products to evaluate it with expected behavior. It includes
black box testing methodology such as system testing and unit testing. The testing method
ST-CH-4 [Make UR Own Style---9145069310]
evaluate theproduct with respect to requirements defined, designs created and mark it as
pass' or_fail. This technique establishes_fitnessfor use' view.
Operational Techniques: Operational techniques typically include auditing work products
and projectsto understand whether the processes defined for-development /testing are
being followed correctly or not, and alsowhether they are effeçtive or not. t also
includesrevisiting the defects before and after fixing and anàlyai_. Operational technique
may include smoke testing and sanity testing of a work product.
OR
Different techniques to find the defects are:
 TEMPLATE
REPORT
DEFECT ANS:-
TheAfter Q.Describe
release/build
Inenvironment,
developers
However, includes + +
most purpose
uncovering Severity
respectivelyPriority
Defect
companies, High/Medium/Low
in all
general, can ofa
defect
number, different
the
template: whichwhich
replicate a
defect information
a
a defecttype, is
defect open/close template describes
related
defect report
the (bug), how A
based
defect
reporting
report defect needed to
is it on
testers was
to dates, report with defect the
the impact
can easilystatedetected, to
tool its
generate reproduce impactfixing
consist the documents
problem attribute
is and of
used
problemjas
fix who urgency
urgency. the
of it. aarea,
dtheelermerits the defect
tefallowing formal
eteçtedit,priority,severity,problem, an
problemanomaly at
Severity
which on
clèarly
defect
the
elements. as including
description, application
the
Priority
report. discovered
ofpossible defect
a
report could
the
test during
should
so author,
can thatstatus, be
vary. be
testing.
fixed
etc.
 Attachments
Severity
Defect
Remarks Expected Replicate
Steps to
Deseription
Result
Actual Summnary
Version
Detected
Build
Module
Version
Release
Product Project ID

Resuits|

Severity Any Attach The actual

Number
The steps.
the Step
comprehensive.step |Detailed
by but possible
Repeating wihoutbutSumiaryI.2.3.5)
(e.g.Build ProdICt
Release
Specific nane. Project
name,LUnique
addition¡l expected
any version
of
description mÍduleversion identifier
result
the additional received you anything of
results. description the
comments
Defect. of
defect. the of of given
or of the
informnation product the
using the Keep prcoduct.
product
of to
on
waythe defect. the
the conplex this where
vhen defect.
defect. where (e.g.
Iike to Describe asclear
yOu the
1.2.3) (Usually
screenshots reproduce words. defect the
and
fol}owed
defect
cOncise.
Keep much 3s was
Automated)
the was
and the detected
steps.
defect. simple it detected.
logs.
appropriate which of
measurement
management
information
Engineering
by
means
the Process
draw the clear
supply Matric
are
Meds to gives To improve
totality metrics
To Test
tracking. and
5.4:
in Test product
MMeasurement Fig.
analvzed attribute. techniques
Applied and
products
services
ProcesS
of based
the to
part
be of
measurement".
integral an readiness
to
have measuring
evaluating
that services on processes,
Paul engineering
processes,
measurement
theproduct.
andata working
measurement by
is
collected of
parameters or into
measured. and given
"standards
describingthe for to andimprove
visibility productS supply reguired
applied
of used a
Metrics
is information
The completenessMetrics.metrics to
be of
key
data. as forcanthe unit
Metric is to supplied
if
of defined provides processes, Software
Software
which
services services
measurement usedquality standard
of results.
"software
management
set unit and techniqueinformatio
Metric?
be
themetrics of
software and and
can software
aCollecting
conclusions.
a quality as
is
a
is
quantifiesDefinition
termedGoodman,
productsproducts
a Metrics
Metric Metric
based
The is Testthe the
What is
andthe
 a is tha a such of
some it to givingwhat improve set
controling,
likely engineering
Software
processes meet that same process.
of therebypredict
size is
what
affect.help can areas
improved. The orto
or By canto we the calculations.
effectively,
capacity,processes.
predict they
visible, process
changes, products
improvements. what
ldent
Understanding we of me
to
5.5
Fig.
Improvement
relationships,
Control entities be Some
dimension, to more the also monitored
to
relate
trends
engineering in appropriate
canmaking. points orformulae
and
process changes
the activities process continuousmay
amount, observe Software the decision data progress parameters
practices. metrics a and
making appropriate
software of of appropriate
a observes measured
aspectsunderstanding
the project,
extent, process, among in and its
our and
controlling
part
in making bydifferent
increasing
modifyingand
as the
measure make a
help theplanning the an
data
processes activities
actions
analysis
ofthe using
tracked in
of the activities relationships
making data
to
raw between pre
measured;
indication an correspondingly, points;future
the
measurements
of by
forstatus
on software and corrective
be on
for process correlation done
element process ourbased following in
help goals data to
product
be be
the
quantitative action from
information for
process. the their improvediscussion,the on mustbe at
Measurement: Metricsbaselines,By based the used
taking must
assess theammong activities of
key corrective
are
the play the understanding
and betweenfromn parame
effect help
attribute
Or of measurements Similarly, be canderived Theright
analy
product one can
is
relationships for happen
Understanding: information
uses
are:
alsounderstanding this Using Improvement:
3. anddata can
Measurements
take involved.
entities 5.5.
needed Relationship
isMeasurement Measurements the of Metrics cause measuremen
a Software
of
Need that Fig. derive y
basis Control:
to product. theare right
of and modifying
meanthappen better ikely
goals.
is in
measures. AnyHowCS TheThe
Visible Iastly, thement shown
Our Th
On 1. 2. 1. 2.
.
 dtasks Once, results
engineer. performance An Apart
Automation
and performed software.
Automation whenAutomated Automation Testing Testing
5.1.2 Software
effectiveness, processes. catch in
delivered Automation
human
Every Automated
tormalized execute
Developing of
f automated money and
sible
tomated development
to from the them
re the Thistester software
theyinvolvement the
in
regression software
expected
comparison manually, Testing testing software often before "manual testing test
is software
testing and processefficiency
withtests the
stress writes cases and
g is which reappear, always developmnent th e use
anual are tool quickly used
involves or is
behavior testing,
point testing product
testing reducing
automating of is to
created scripts and interaction
strategies, called test
is is to to is
an manual
able and coverage has process", the
sting. of automationre-run also is even
al Automation is as the
they and to view. repeatedly. and the released defects.group automationsoftware
known with
playback testing. the uses in
tools thenumber
cause can report It ofbest unskilled, currently manual
nt increases test your the Testtests
easily of as way but and is
the testing
) scenariossoftware a Test best called
pre-recorded they artifacts
its exists testing. of
5.3
of success manual software to engineers
this, be Automation manual repetitive testing test
repeated the increase always products, test
of is to cases.
ul
eable test also process) that testing.) inautomation. )
or test strive thatprocess
the
were testing or
failure coverage;
and used the creep augment company Using
and is the redundant yet
to currently
nt predefined
they to
of test any
these improve Fig. or Motive
agers canmanual execution or
the 5.2: Test reduce autormation
tasks.)
organization.
be in
extended actions, application
Automation use.
of Testing
s. accuracy, the autormation
have This
Script need tool Tools
tests
test
toa automation Test
found to compare requires
saves Test and
perform from
Testing of for
manual saving Measurements
testing (W-16, 17)
that time load,
the that
time
or a to
Disadvantages of Automation Testing:
1. Proficiency is required to write the automation test scripts.
2. Debugging the test script is major issue. If any error is present in the test script, sometimes it
may lead to deadly consequences.
3. Test maintenance is costly in case of playback methods. Even though a minor change occurs in
the GUI, the test script has to be rerecorded or replaced by a new test script.
4. Maintenance of test data files is difficult, if the test script tests more screens.
eting and ManualTesting: S-17, 18)
 hap
Criteria
ts.
kills,
4.and3.
trequirement,
echnology Meeting
ectations, 2.requirements
1.Theautomation. For 5.3
9. 8. 7. 6. 5.
* 3. 2 1.
appropriate
Selecting haing
categories for all Select
the SelectMatch Not Test tools Test
Lest
the SDLC languages, developed Developing meet Free SELECTING
Selecting alltools
above a athe test aretools tools tool 1dentified
The phase, tool tool needs the
of form toolgenerally sold are tool
which tools properly require th e test
criteria
requirements to customizing
Test the strong
the its to by in-house not tool for
toolsbetter.
its run vendors well the A
appropriate is strong automation. is
Tools: basisreasons,
for testingappropriate on do TESTING
affordable not trained. leaves They tools
supportedrequirements an
selecting for al l the important
should
toolsadequate tools platforms. meet training. are the tend takes
tool expensive.
also SDLC i.e. use, Training
all fo r organization, and
T00L
testselection.cover to
time,
choose i.e. the use, Test have aspect
get of
tools change. phase
focus requirements
before automation
and
Evanphase what
both usually poor
are: of
needs means the adding thethrough test to
the tool out
selecting tools automate,
short to twithin he involves documentationautomation so
be extensions for cannot becomein-house ol.
provided
term methods automation.
the tool a
and it getting
successtul related
budget is
or unusable. tools for
long for of
necessary and several
plug-ins Can
testing of familiar thus, que
selecting
term the uniess bereasons
software to for once less ons
requirements. changes the ote
know the with expensive as
the person
whothe
tool. people given
rightaccordingproject. its the Ciolce
tool scrintinusing and below:
These of
for to the
 este
c1 MANUAL TESTING AND AUTOMATION TESTING
S11 Manual Testing nat

Manual testing is the oldest and most rigorous type of software testing (Manual testing requires a is
tester to perform manual test operations on the software without the help of Test automation)
(e Manual software testing is performed by a human sitting in front of a computer carefully going
through application screens, trying various usageand input combinations,comparing the results to out

the expected behavior and recording their observations.

[$.1)
 identify software
to texplore
he testers testing
asexploratory includes also testing Manyal testing.
ompleteness
of theensure Software
to the testscenarios
to test cases
or test plan, test usTesters
e
testingAcceptance User and
testing System testing,Integration testing, unit liketesting manual fstages
or different e
ar(There
bug. behavior
or un-expected any
identify Software
to the test and user end an of
role the over takes tester testing,
the of
type this n
script. any or
automated
tool any using without manually
i.e. software the testing
of includes
the testing CManual
configurations. hardware environments
and operating multiple situations
like
other andchanges code source for cycles
development during often repeated are tests Manual
easurements andTools Testing 5.2 Testing Software
 thenreliable more Manual is 6.
testing. manual entered
in are who people new folearn
r toEasy 5.
cost.limited covered
in Itis 4.
movement. project according to case test our added and reduce Easily
we 3.
testing. manual productive begin expense
to and times requires
less It 2.
project. big and small both inuse testing
becan Manual 1.
Testing: Manual Advantages
of
 REPORTING
TEST
3.4
a
2. Summary Comprehensive
Thererequires
development constant
Testing Atwo-way
3. test
Test
incidence defects
of repository.
(i) running
Test
(1)
(iü)) There forTest (v) (iv) (iii) (ii) progress are report
each mapping
release. Defects A Cycle Incidentreports tw o
hase-wise
alsoFinal Summary Progress
Any
Outstanding
are summarycycle, are
throughcertain typesteam. test is
alled tw ovariations (defects)
Report: Is
test A that gives: encountered. defectReport: (also any betiween
report
types from of
Test report
mmary as test Report: of thetests reports description,
defects were the Test is called reporting
has
lease ofobserved the highlighted is
that various in It all re
summary, test uncovered activities cycles, projects a istest
The previous
that unique
Communication A a or of
report,summarízes
test summary final communication test
completion is those
inare cycles, a
carried each take in ID
incident
ort". which
communication explanation
which
effort yetcycle
step during the and means things
to to it
cycleplace
reports: the in or be is of
has is the that out to
test this reports).
schedule
produce results test a fixed using
be in report together.
between
all currentcycle, during summary
units used that that achieving or
cycle
expected
the a to is
at of (that in
this differemt of happens are
justification the
details test cycle based that identified nothing
the is test
report. this
to cycle,
can cycle. to required test
end cycle
ofrecommend be in on stabilize. cycles. through
their build communication. team the
testing of is used andterms the but i.e.,
phase.
every a A
best severity of oftest an
for A incident. the test and status
done defects test the entry
summary the
future cycle testing
product.
cycle
incident other
of
bysuitability and Themade
all fixed, entails Aa
planning). impact,
high cycle reports teams S-17,18)
testW-16;
phases report. report,
As in
planning
the project.
of at impact the as like
and a an and
produt product
the defert
teams test the
end and test when
 the and
Management
Test
case, executed,
this
(in was
specifications
includes: include:
reasons), what
plan),
and
should
This(with
phase. testplanned
planned.
tests original
or run release
cycle was andtests.
be original descriptions,
activities thewhat the for
test not
in by recommenda
the could the not between uncovered
during
thebut in were
3.19
was se
from
run taken cause
out be what (thát and
out
carried runtime rootdefects
plan.include:
to assessme
carriedfrom
planned from any and release ofRecom
present: updated),
wereand
should theassessment
activities tests deviations
activities effort withof
were that impact
should to failed, release"
results
be tests
Modifications
in
the that should
report: Differences Comprehens
Additional
of thetests other thatofSeverity
summary
of of for
Summary
TestSofintwgarsummary
TCDB
e Variance
The Any Tests "Fit
Ki) (ii) (iv) (v)
A (i) (ii) (1) (ii)
A 3.
2 4.
ect.
n Inthe In
MANAGEMENT cases TestTEST3.2
this
typical the
objectives.
managementsub-classes and
ection,
ese previous and
project test
g results
we Section
genment is
will
to a
ts look 3.1,method
enable
at we
some
accessibility
areconsidered of
issues
organising
al
of
the in
testing.
pects testing and
s test
reuse.
that asassets
at project a
ould and
an artifacts
e be in
its
aken
an own such
- care right as
test
of and
in
e requirements,
ng address
WN-17))
(S-16,
SOme
ucn
tes
O1
a