• Documentation
  • Tutorials
  • Case studies
  • Blogs
  • Product

What's on this Page

  • Setup
  • Declaring a cypress Keyword
  • Creating a plan with cypress Keywords
  • Running a plan with cypress Keywords
  • Limitations
  • step
  • Plugins
  • cypress Plugin
Categories: PLUGINS
This article references one of our previous releases, click here to go to our latest version instead.

cypress Plugin

This page will show you how to configure and use the Step plugin for cypress. The cypress plugin allows you to declare Step Keywords that run cypress commands and thus leverage the combined power of Step and cypress.

Setup

The cypress plugin is a beta feature currently incubating as part of the enterprise version of Step. The cypress plugin is enabled per default in Step enterprise. To use the plugin you simply have to install cypress on the Step Agents you’ll want to run cypress Keywords on:

  • Install cypress following the official cypress documentation

  • Test the installation

npx cypress open

That’s it!

Declaring a cypress Keyword

You can declare cypress Keywords and use these Keywords within Plans like any other Step Keyword. To declare a cypress Keyword:

  • Open Step

  • Navigate to Keywords

  • Click “New keyword”

  • On the Keyword creation dialog

    • Enter a name for your Keyword

    • Select “cypress” as Keyword type. If you don’t find “cypress” in the list, you might be using the open-source edition of Step

    • Enter the cypress command or script. Example: cy.visit(“https://exense.ch”)

    • Enter the base URL related to the command. Important: the base URL should match with the one used within the command

Creating a plan with cypress Keywords

Creating a Plan with cypress Keywords is as easy as with any other Keyword.

  • Open Step

  • Navigate to Plans

  • Create a new Plan

  • Select your cypress Keywords from the Keyword list and add them to the plan

Running a plan with cypress Keywords

Once you’ve created your Plan, run it by clicking on the Play button as documented here

The execution report looks the same as with other Keywords. If the Parameter debug is to true a screenshot will be generated after each Keyword execution.

In addition to the measurement of the whole Keyword response time, a performance measurement for each cypress command is generated and can be analyzed under the Performance tab

Limitations

In its current beta version the cypress plugin has following limitations:

  • Keyword inputs and outputs are not supported. Support for inputs will be added soon

  • Only native cypress commands are supported. Support for custom commands will be added soon

  • Using Keywords with different Base URLs within one test case is not supported

See Also

  • .NET agent
  • JMeter
  • Node.js agent
  • PDF and Image compare
  • SoapUI
  • Home
  • Whats new?
  • Admin guide
  • User guide
  • Developer guide
  • Plugins
    • .NET agent
    • cypress Plugin
    • Node.js agent
    • ALM
    • Azure DevOps
    • Jira Xray
    • Async packages
    • JMeter
    • SoapUI
    • PDF and Image compare
    • Artifact repository connector
    • Analytics and external DBs
  • Libraries
Step Logo
    • Documentation
    • Tutorials
    • Case studies
    • Blogs
    • Product
    • Home
    • Whats new?
    • Admin guide
    • User guide
    • Developer guide
    • Plugins
      • .NET agent
      • cypress Plugin
      • Node.js agent
      • ALM
      • Azure DevOps
      • Jira Xray
      • Async packages
      • JMeter
      • SoapUI
      • PDF and Image compare
      • Artifact repository connector
      • Analytics and external DBs
    • Libraries