3.Your manager would like to
introduce exploratory testing to your agile team. He has received the following
suggestions on how to proceed from previous colleagues:
i. User stories are assigned to testers who are completely new to the user story. There is allotted 120 minutes allocated to complete exploratory testing on the user story. Testers do not need to document tests, or test results, but do need to log defects if any are encountered.
ii. User stories are assigned to testers who have already completed risk based testing on the same areas. There is allotted 120 minutes allocated to complete exploratory testing for this user story. The team expects at the end of the 120 minutes to have a list of test ideas, including data and actors, results and issues encountered, and list of defects to be logged in the defect management tool
iii. A user story is assigned to business representative. The business representative is told to use the system like the customer would on a day-to-day basis. If issues are encountered, the business representative is told to inform the tester, so that they can prioritize and log the defect.
iv. A user story is assigned to a tester for exploratory testing. Tester is told to learn the functionality of the user story, to make sure the functionality is correct and to include negative testing. There is no set deadline for this exploratory testing to be complete; it depends on what is found by the tester. Documentation is not necessary, but defects need to be logged in defect tracking tool.
Your manager presents you with his conclusions about how best to introduce exploratory testing to an agile team. Which one of your manager's conclusions is correct?
A Scenario i IS NOT the bestway because: In exploratory testing, test design and test execution happen atthe same time but are guided by a documented test charter that includes actors,test conditions, test data, etc. Test results are also documented and willguide the next test.
B Scenario ii IS the best way because: In this case, the testers have knowledge of the user story already, which will help them come up with test conditions and ideas. The team is using timeboxed exploratory test sessions. The team is expected to document test conditions, data, and user information, and to log results of the test. Issues are logged in a defect tracking tool just like any other test technique.
C Scenario iii IS NOT the best way because: This could be describing system acceptance testing, but not exploratory testing.
D Scenario iv IS NOT the best way because: Documentation is necessary for exploratory testing, and testers must log test ideas and results of testing. The results of testing are used to guide future exploratory testing.