cypress-cucumber-preprocessor 4.1.0 - TSX and Multiline Step Arguments support

We've just released a new version of the cypress-cucumber-preprocessor package.

Multiline Step Arguments:

Thanks to @Enrico126 it allows usage of multiline step arguments, as showcased with a simple .feature example:

  Scenario Outline: DocString
    When I use DocString with argument like this:
      You have been granted <Role> rights.
      -The Admins
    Then I should have a string with argument "<Role>"

    |  Role     |
    |  Manager  |
    |  Admin    |

and matching step definition:

let argString = "";

When("I use DocString with argument like this:", (dataString) => {
  argString = dataString;

Then(/^I should have a string with argument "([^"]*)"$/, function (argument) {

TSX support:

Thanks to @mallison you should be able to use .tsx files as your step definitions. As noted by @azamuddin this change also allows the use of @cypress/react to test react components in isolation with cucumber.

Let me know if you have any questions or thoughts in the comments below.

Let us help you on your journey to Quality Faster

We at specialize in helping our clients get more for less. We can get you to the holy grail of continuous deployment where every commit can go to production — and yes, even for large enterprises.

Feel free to schedule a call or send us a message below to see how we can help.

User icon
Envelope icon


Schedule a 30m call
  • Adding TypeScript to the official Apollo Platform Tutorial app

    In todays video I go through a preparation of the official Apollo Platform Tutorial App for adding Chimp to it. I decided to divide that task into two steps - first is adding TypeScript to the codebase. Watch me work, struggle, fly through code, hopefully you will learn some tricks :)

  • AWS CDK Lambda and DynamoDB dependency management

    A discussion about issues we've stumbled upon and a solution that simplified our CDK workflow.

  • Chimp 4.0 - resolvers for extended federated types

    The Chimp 3.0 and previous versions always generated resolveReferences resolvers for all federated types. It turned out to be excessive, so we make it configurable.