feature startup speed

Longtime cucumber user, but relatively new to cypress so first, thank you for this!

It seems that cypress resets the world between each feature file. That results in some noisy logging after each feature…

  Running: user-dropdown/logout.feature...                                               (24 of 25) 

  [▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬]

  2 passing (3s)


  (Results)

  ┌────────────────────────────────────────────┐
  │ Tests:        2                            │
  │ Passing:      2                            │
  │ Failing:      0                            │
  │ Pending:      0                            │
  │ Skipped:      0                            │
  │ Screenshots:  0                            │
  │ Video:        true                         │
  │ Duration:     3 seconds                    │
  │ Spec Ran:     user-dropdown/logout.feature │
  └────────────────────────────────────────────┘

I could live with the logging, but my main problem is that this more than doubles the execution time for the test run of all features.

The tests are pretty fast once they get going, but there is a noticeable lag to get them started.

Is there any way to organization features and/or scenarios in a way that it runs them all in the same “test run”.

I am running the oldschool step definition structure and I noticed the bit about startup speed in the readme. Is that what I’m seeing here? We have 110 step definitions used across 25 feature files.

[darrinholst]

@lgandecki sorry for the delay. Here is an example repo using the features from this repo itself

https://github.com/dholst/cypress-cucumber-preprocessor-example.

I added an index.features file and specified which way I want to run them in the --spec config.

Here is the normal test run - https://gist.github.com/darrinholst/be3eaf9016aa63c094111e0744d56ca9 which took 4.25 minutes.

Here is the run with my changes - https://gist.github.com/darrinholst/80ea8820a12b0185e7d36f2ac7f03bb1 which took 22 seconds.

You’ll notice that there was 1 failure there which is due to this project’s take on isolated step definitions. Since all the features run in one context this way all the step definitions have to be loaded which kind of breaks the isolation. I think there is probably a way to fix it by passing all the required step definitions to the createTestsFromFeature function and requiring them in there…maybe.

I don’t use that feature and I’d be curious to know what existing cucumber users think of it. The official stance from cucumber developers themselves is that it’s an anti-pattern, but that’s a discussion for another day. 😄

I hope the example repo and the results show what I was trying to do and the speed improvements that are possible.

[amitguptagwl]

1. To use bundled file, should I create empty index.features file in features folder?

npx cypress run --spec \"**/*.features\"

Above command hangs.

1. What would be the syntax if I want to use while giving the list of tags to run

npx cypress-tags run -e TAGS='not @Ignore' --spec \"**/*.features\"