Flowriter docs
Login to Flowriter
  • Getting started
    • What is Flowriter?
    • Create a free trial account
    • Sign in
    • Supported languages
    • Help & support
    • Log out
  • Account settings
    • Billing details
    • Languages
    • Security
    • Close your account & delete all data
  • Buying & using credits
    • Use credits
    • Buy credits
    • View credit balance & usage
  • Epics
    • Epics in Flowriter
    • Add an Epic
    • Automatically suggest Stories
    • Card and List views
    • Generate content for multiple stories
    • Export an Epic's Stories
    • Rename an Epic
    • Delete an Epic
    • Bulk delete stories in an Epic
  • User Stories
    • User Stories in Flowriter
    • Viewing Stories & progress
    • Add a story
    • Automatically build flowchart and Acceptance Criteria
    • Navigating a Story's sections
    • Rename a Story
    • Change a Story's language
  • Working with flowcharts
    • Flowcharts in Flowriter
    • Flowchart capabilities & requirements
    • Automatically generate a flowchart
    • Manually create a flowchart
    • Edit a flowchart
    • Save changes to a flowchart
  • Generate Acceptance Criteria
    • User Journeys & Acceptance Criteria in Flowriter
    • Generate Acceptance Criteria
    • Copy User Journeys & Acceptance Criteria
    • Export User Journeys & Acceptance Criteria
  • Generate Test Scripts
    • Test Scripts in Flowriter
    • Generate Test Scripts
    • Copy Test Scripts
    • Export Test Scripts
  • Data security & privacy
    • Our security practices
  • Legal
    • Terms & conditions
    • Privacy Policy
    • Cookie Policy
Powered by GitBook
On this page
  • Automation frameworks/tools
  • Manual test steps
  1. Generate Test Scripts

Test Scripts in Flowriter

PreviousExport User Journeys & Acceptance CriteriaNextGenerate Test Scripts

Last updated 5 months ago

Flowriter can analyze a Story's Acceptance Criteria and generate Step Definition test scripts, in Javascript.

These can be used to save time when creating automated tests to validate the implementation of the feature documented in the Story.

Step Definitions connect steps in Gherkin -style Acceptance Criteria to programming code.

A Step Definition contains an expression that links it to one or more Gherkin steps. When the Cucumber test automation tool executes a Gherkin step in a scenario, it will look for a matching step definition to execute.

Flowriter will generate sample Step Definition test scripts, in Javascript, for each Scenario generated from the Story flowchart.

For more information about Step Definitions used in the Cucumber test automation tool, see

Automation frameworks/tools

Step Definition test scripts do not prescribe the test automation framework - different tools may be used to automate testing.

If your feature relates to an app, Flowriter will attempt to determine whether it is a web or mobile app and include sample Selenium or Appium Javascript code in the Step Definition test scripts.

Manual test steps

Where Flowriter cannot determine the technical nature of the feature, or it includes steps that cannot normally be automatically controlled by a third-party automation framework, it will include comments in the source code to indicate this.

For example, is a popular tool for controlling web apps in automated tests, while is a popular tool for controlling mobile apps in automated tests.

Selenium
Appium
Cucumber Step Definitions