Skip to main content
Sign In |
  Help (new window)

Enterprise MSF Agile (with CobiT)

Go Search
Home
  
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Conduct Exploratory Testing (Test a Quality of Service Requirement)  

Activity - Conduct Exploratory Testing (Test a Quality of Service Requirement)

View All Site Content

Recent Changes
Activity Information

Conduct Exploratory Testing

Test a Quality of Service RequirementConduct Exploratory Testing

Description

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.

Roles

PerformerTester

Attributes

CategoriesAccepted Build, MSF Agile Principles - Empower Team Members , MSF Agile Principles - Establish Clear Accountability, Build, User Experience, MSF Agile Principles - Invest in Quality , MSF Agile Principles - Work Toward a Shared Vision , AI2.8 Software Quality Assurance

Steps

  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.

Inputs and Outputs

WorkProductInputOutputAllowable States
Persona(none)

Successors

TypeNameDependency Type
Open a BugFinish-Start

Other Instances

Instance Parent
Enterprise MSF Agile (with CobiT)Test a Scenario

Last modified at 1/17/2008 11:18 PM  by Administrator