Running cucumber in artillery.io

[CHCSkedroski]

I was wondering if it is possible to integrate artillery with cucumber so that you can run cucumber based scenarios with artillerys reporting and virtual user concepts

[hassy]

I haven't seen anything that integrates Artillery & Cucumber, but it may be possible using Artillery's engine API.

Is the idea that you already have a test suite written in Cucumber, and you'd like to run those tests as load tests with Artillery?

Would love to understand the use case better!

[CHCSkedroski]

yes that is correct we have some BDD and user workflows written in cucumber and would like to run those with load in artillery

[hassy]

got it, thanks! and are those tests using Selenium under the hood? in theory, if the tests only depend on what can be installed from npm, it should be possible to run them in Artillery. (for example our new playwrigtht engine takes advantage of that to run load tests with real browsers)

[CHCSkedroski]

yes they would be using selenium under the hood thanks for the insight

[vikramgupta0608]

any update on this issue , do we able to integrate artillery with cucumber ?

[bernardobridge]

Hello @vikramgupta0608 ! We don't currently support cucumber out of the box, as Artillery has its own DSL in YAML.

But as Hassy mentioned, it would be possible for you to write a custom engine that takes a Cucumber scenario and runs it, rather than using the HTTP engine by default. The Playwright engine (now lives here) mentioned above would be a good starting point - it exposes a flowFunction API that has access to the Playwright API. You could try something similar using cucumber-js.

[Husain-Syedali]

Is there any update on the above cucumber query?
Please let me know if artillery supports cucumber suites, I am looking forward to execute all my playwright+Cucumber based suites using artillery.

[hassy]

There's no support for using Cucumber and Playwright with Artillery at the moment, or plans to add it. It may be possible to do via Artillery's extension APIs but it's not something we're looking at doing as a core feature or integration.