• Documentation
  • Tutorials
  • Case studies
  • White papers
  • Product

What's on this Page

  • Create a plain text plan
  • Plain text plan editor
  • Plain text syntax
  • step
  • User guide
  • Plans
  • Plain text plans
Categories: USER GUIDE PLANS
This article references one of our previous releases, click here to go to our latest version instead.

Plain text plans

In addition to the Visual Plan editor step comes along with a full-featured parser which enables the creation of Plans using a plain-text human-friendly syntax.

The plain-text format has different advantages over the Visual interface. Using the plain-text format makes it possible to manage Plans in a same manner as code and thus enables the use of versioning (git, or any other versioning system), text editors, etc. It also enables the integration with classical Test-Management Tools initially developped for manual test specification and thus based on plain-text test-cases specifications. In particular the plain-text syntax is used natively by the ALM Plugin for step. The plain-text format allows the implementation of Plans using exactly the same Controls and Keywords as the Visual interface and has nearly no limitations compared to the Visual interface.

Create a plain text plan

As of 3.13 you can also create plain text plans directly step.

To create a plain text plan in step, navigate to “Plans” and click “New Plan”

On the plan creation dialog select the plan type “Plain text”, enter a plan name and click “Save and edit”:

The plain text plan editor will be opened:

Plain text plan editor

The plain text plan editor is structured as follow:

  • Source: the text editor where you write your plan using the plain text syntax.
  • Tree: when writing your plan in the “Source” panel, step will try to compile your plan. If compilation succeeds, the compiled plan will be displayed as tree in the “Tree” panel. Currently the “Tree” panel is displayed in read-only mode. Future version of step may allow bidirectional edition between “source” and “tree”.
  • Available components: this panel give access to the 3 types of libraries. You can add components to your plan by clicking the + buttons of the items shown in the different library tabs. They will then be automatically added to the current line of your plan using the corresponding syntax. Currently only “Other plans” and “Keywords” can be added to the plan using this feature. Generating the syntax for Controls will be added in future releases of step
    • Controls: listing the available Controls
    • Keywords: listing the registered Keywords
    • Other plans: listing the Plans which might be referenced to build modular Plans

Plan text plan can be managed/used as any other Plan and can thus be also referenced by other plan, executed, etc.

Plain text syntax

You will find the details of the plain text syntax on the Controls page. In addition, you can precede any line by a comment, this will set the name of the resulting node. The following screenshot illustrate the syntax to set this name either in a static or dynamic way.

As this name is also used when generating report nodes during an execution it might be very helpful to set it adequately

See Also

  • Controls
  • Keywords calls
  • Plan modularity
  • Java Plan API
  • Visual Plan editor
  • Getting Started
    • Overview
    • Quick setup (install)
    • Quick setup (SaaS)
    • My first Execution
    • Browser automation
    • Real-world scenario
    • Scaling out
  • Whats new?
    • Release notes
    • Roadmap
    • Weekly news
  • Admin guide
    • Database installation
    • Controller installation
    • Agent installation
    • Requirements
    • Backup & Restore
    • Housekeeping
    • Migration
    • Customization
    • Project management
    • Admin Views
    • Troubleshooting
    • Encryption Manager
  • User guide
    • Keywords
    • Plans
      • Keywords calls
      • Controls
      • Plan modularity
      • Visual Plan editor
      • Plain text plans
      • Java Plan API
    • Executions
    • Notifications
    • Parameters
    • Dashboards
    • Monitoring
    • Scheduler
    • User Preferences
    • Event Broker Monitor
    • Executable bundles
    • Import/Export entities
  • Developer guide
    • Dev Overview
    • Keyword API
    • Measurement API
    • step client API
    • Event Broker API
  • Plugins
    • .NET agent
    • cypress Plugin
    • Node.js agent
    • ALM
    • Azure DevOps
    • Async packages
    • JMeter
    • SoapUI
    • PDF and Image compare
    • Artifact repository connector
    • Analytics and external DBs
  • Resources
    • Tutorials
    • Case Studies
    • White papers
    • Libraries
Step Logo
    • Documentation
    • Tutorials
    • Case studies
    • White papers
    • Product
    • Getting Started
    • Whats new?
    • Admin guide
    • User guide
    • Developer guide
    • Plugins
    • Resources