Exposure to Exploratory Testing - QAI
Exposure to Exploratory Testing - QAI
Exposure to Exploratory Testing - QAI
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
ET in Different Scenarios<br />
Scenario Drawbacks of TCB ET<br />
Localization Web based project for the<br />
financial institution which needs <strong>to</strong><br />
test its application in 6 different<br />
languages. This has multiple releases<br />
which will be tested in two different<br />
environments SIT and UAT. Timelines<br />
are reduced from 4 months <strong>to</strong> 2<br />
months due <strong>to</strong> reduced scope.<br />
Available Resources at the cus<strong>to</strong>mer<br />
site is a team of 6 which includes a<br />
Test lead other all are tester with 2-3<br />
years of testing experience<br />
• Possibility of Pending task at the<br />
end of timeliness is high.<br />
• High possibility that some<br />
requirements are missed while<br />
preparing the test strategy and the<br />
test cases.<br />
• Ambiguity in reporting the defect<br />
as the no of languages tested is<br />
high.<br />
• With tester handling individual<br />
language there is high possibility of<br />
a critical defect getting missed<br />
which may be also be a defect in<br />
the other language.<br />
• Test lead prepares some charter for<br />
the testing.<br />
• The team will split up in teams or<br />
as individuals and start testing the<br />
application covering all the<br />
requirements.<br />
• Approach is taken down on an<br />
excel or a flowchart which might<br />
help as future reference.<br />
• Helps cover all the requirements<br />
with proper defect report.<br />
BFS-US SSDU Research
Change language