Exposure to Exploratory Testing - QAI

ET in Different Scenarios
Scenario Drawbacks of TCB ET
Consider an Ad-hoc requirement
based project where the
requirements come dynamically
on the fly on call or through mail.
Requirements here refer to rules
which have to be followed while
loading data into the table. To
check if the table is loaded in
accordance to the rules, queries
are run against table to check for
data validation and in case if any
error records found; such records
have to be moved to Error table.
Resources available for the above
scenario are 1 Test Lead and 2 Test
Engineers.
• Agile projects with dynamically
changing requirements impose great
difficulty for TCB in planning and
strategizing approaches.
• Defect detection rate is low as the
tester is unaware of the inner
functionality of the product.
• Incorporation of requirements in the
correct place is difficult.
• Requirements are documented as a
Flowchart to get a clear picture of
all the tests to be made.
• ET maintains minimum
documentation and mainly focus
on detecting more defects within
fixed timelines.
• Diverse testing techniques are
followed to carry out testing.
• Skilled Exploratory Testers follow
their own approach to extract the
output with zero or minimal
planning.
• Exploratory Testers conduct
brainstorming sessions with a
group to generate various ideas to
perform testing.
BFS-US SSDU Research