User Stories in Flowriter
Last updated
Last updated
A User Story in Agile documentation describes a small, specific piece of functionality from the user's perspective.
While an Epic is like a big project goal (e.g., "Build a shopping cart"), the User Stories inside it are the smaller, specific tasks needed to achieve it (e.g., "Add items to cart," "Remove items from cart," "Calculate total").
In Flowriter, User Stories ("Stories", or "Story") are contained in Epics. A Story in Flowriter has the following features.
This can be anything you like. User Stories are often named using Role, Goal, and Benefit statements e.g. "As a user...I want ... so that..." .
You can (but don't need to) use that format for the Story name in Flowriter. A Role, Goal, and Benefit statement will be automatically generated by Flowriter as part of the Acceptance Criteria later.
Automatically generated Story content such as flowcharts, Acceptance Criteria, and Test Script comments are generated in the default content generation language. This is first set when you created your account, and can be changed at any time in the .
A Story's flowchart is where you visually define the actions, decisions, and notes about how a user or system might navigate a feature or service.
Flowriter will analyze your flowchart to automatically extract User Journeys, write Acceptance Criteria, and prepare Test Scripts to implement and test all the potential actions and outcomes of the feature.
User Journeys outline the steps and decisions users make to achieve their goals, and inform the Acceptance Criteria:
During the generation of the Acceptance Criteria, Flowriter analyzes your flowchart and identifies all possible "paths" that a user (or system) could take when using the feature.
These are summarised into separate Goals, each consisting of a series of steps and decisions.
A Story's Acceptance Criteria is automatically generated, and consists of two (2) parts:
This summarizes the overall feature described in the flowchart and identified User Journeys, and is presented in this format:
As a [user/system/...] ... I want to ... So that ...
Flowriter can analyze a Story's Acceptance Criteria and generate Step Definition test scripts in Javascript:
See:
See:
These defines how the feature should behave based on User Journeys. These criteria are generated in , a structured format that can be read by both humans and scripts.
Step Definitions connect steps in Gherkin -style Acceptance Criteria to programming code. In most cases, a Test Script is generated per Scenario in the feature. They can be used to kick start automated testing of the feature described in the Story, using tools like .
