Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| ### Next Steps Open a Bug Brainstorm Scenarios Brainstorm Quality of Service Requirements |
| Activity: Conduct Exploratory Testing
Tester
Business Analyst
|  |  |  | Test a Quality of Service Requirement |  |
|  | Participating Roles Responsible: Tester Business Analyst
### Overview Exploratory testing is a systematic way of testing a product without a predetermined set of tests. There are many heuristics that can be employed to conduct exploratory testing. These heuristics include using personas, adjectives and adverbs, variable analysis, range searching, and testing various states. The heuristic provided in this guidance describes how a product is tested from the point of view of a persona with the purpose of generating new requirements. To perform exploratory testing in this manner, assume a persona and work through the functionality of the system attempting to reach specific goals. If new goals are discovered or functionality is not efficient to suit the needs of the personas, add new or modify existing scenarios to suit these needs. Limit the exploratory testing sessions to no more than two hours. # Entry Criteria A build is ready to be tested for new requirements or bugs. Dependencies: The personas are published on the project portal. # Sub-Activities
1 | Establish Session Length | Set the period of time for the exploratory testing session. This period should be no less than a half an hour and no greater than two hours. Set the goals for the session. Start a session log.
2 | Meet Persona Expectations | Select a persona from the set of published personas. Run through the existing functionality to make sure persona expectations are met.
3 | Envision New Goals | Examine the challenges the persona faces. If the challenges might be too difficult to overcome, open a new bug or add new scenario or quality of service entries to the scenario list. Make changes to existing scenarios or quality of service requirements and track the changes to appropriately reflect the new understanding. Look for new goals or missing functionality necessary to fulfill the product vision. Add new scenarios or quality of service requirement entries to the scenario list. Look for quality of service concerns and add new quality of service requirements to the quality of service requirement list.
# Exit Criteria
| New scenario and/or quality of service requirements have been added to reflect the new understanding of the system.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |