User Story Testing provides positive confirmation feedback, making it the perfect complement to standard exploratory bug reports. User Stories are properties of Features, and each may be executed a maximum of three times.
User Story Testing leverages the low maintenance and crowd-creativity of guided exploratory testing, as well as the positive validation and confidence that comes with test cases.
Getting Started - Writing User Stories
- Go to the Manage Features page for the desired Product.
- Click on the 3 dots > Edit > Add User Story
- Write the User Story. (see Best Practices below)
Creating a Test with User Stories
- Add User Stories to any test type, except Usability Tests.
- Select desired User Stories to add them to the scope of a test.
Viewing User Story Test Results
- View results on the Overview tab
- Click on a User Story to reveal individual execution information
Best Practices When Writing User Stories
- Use goal-oriented language, not step-oriented.
- Write from a user perspective.
- Define one objective Pass/Fail criteria per User Story.
- User Story scope is small enough that it can be executed in a few minutes or less.
- Always include expected behavior language in the Feature description in addition to the User Stories.
Optimal Use Cases
- Exploratory testing results have been valuable, but you would like positive validation feedback on a subset of the functionality.
- Scheduled Test results are consistently yielding little to no bugs.
- Likelihood of finding bugs is low due to mature product or small-scope tests.