|
|
|
|
|
|
|
|
|
MSF for CMMI Process Improvement > Wiki Pages > Activity - Conduct Exploratory Testing
|
Activity - Conduct Exploratory Testing
|
|
|
|
|
|
Activity Information Conduct Exploratory Testing
DescriptionExploratory testing, also called ad hoc testing, is conducted by the tester assuming the persona of the user and exercising the product as that persona would. Exploratory testing can be a very important source of discovery, not just of bugs, but of unforeseen scenarios and quality of service requirements. Capture these in the backlog of the work item database, so that you can use them in planning future iterations. Attributes| Element Categories | [CMMI Cycle 4] Iteration, [CMMI Level 2] CM SP 2.1, [CMMI Level 3] RD SP 1.1, [CMMI QoS 3] User Experience, [CMMI Track 3] Build, [CMMI Track 4] Stabilize | | When | A build contains enough functionality to explore persona usage in certain areas of functionality. | | Entry Criteria | Build:
Enough functionality is ready to explore persona usage of specific areas of the product.
Personas:
Personas are used to guide the exploratory testing. | | Exit Criteria | Scenarios:
New scenarios are added to the scenario list.
Quality of Service Requirements:
New requirements are added to the quality of service requirements list.
Test Result:
A test result is observed during exploratory testing that uncovered a bug in the product. | | Is Required | No |
StepsTimebox the Session:
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. Meet Persona Expectations:
Select a persona from the set of published personas.
Run through the existing functionality to make sure persona expectations are met. 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 or requirements 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 requirements list.
|
Last modified at 12/19/2007 10:37 AM by Administrator
|
|
|
|
 |
|
|
|
|