Exposure to Exploratory Testing - QAI

ET in Different Scenarios
• Illustrates about the application Testing of a shopping site say shopfree.com which details us how a defect can
be turned into a requirement.
Scenario Drawbacks of TCB ET
The site has a homepage and
a payment page which
performs the credential
verification and allows the
user to shop. Here the page
contains OK and CANCEL
buttons apart from the
credentials which helps us to
go ahead into the site and
cancel the application
respectively.
• As the LLD/HLD is followed by the test team,
some basic functionalities might get missed
which might turn into a serious defect.
• During the development of test scripts,
found difficulties like some ended obsolete,
deferred, because of changes in software or
hardware or firmware or incorrect
requirement or technical limitations or
schedule limitations.
• During Execution phase, as a round of 4-5
cycles is done on the same Test cases, Tester
might feel it boring performing the same
tests with occurrence of very less bugs
when compared to the initial cycles.
• Exploratory tester covers all the
aspects of the Homepage and the
payments page.
• The chances of missing any defects
or instances are less as the
Exploratory tester interacts and
explores the application.
• In this context, Tester while testing
the application checks for the
navigation from payments to
homepage.
• As there is no specific link provided
in the page to navigate to the
homepage, this is considered as a
defect which is reported to the
development team which can be a
requirement.
BFS-US SSDU Research