Is every batch supposed to run every feature? about serenity-cucumber-starter HOT 4 CLOSED

Batches are for distributed execution, not parallel execution, and I don't know if they were ever used with Cucumber. Why don't you just use the Cucumber 6 parallel execution?

from serenity-cucumber-starter.

I'd be happy to take a look at it - I think I tried cucumbers built in methods in the past but that was on an older version.

Due to the nature of the software I'm testing (Java Swing-based instead of web), I'm not able to use parallel threads to run multiple tests per machine, but rather have to batch the tests out to a number of VM's that have been set up for that purpose.

from serenity-cucumber-starter.

I guess to be a little more specific - I have a Jenkins pipeline set up that programmatically generates the correct number of runner class files, based on the number of available VM's, before building and executing the test suite with the -Dbatches arg set to that value.

The driver I have to use to automate interactions with the client (UFT from MicroFocus) has to be initialized to the specific machine being used to execute the tests, which I was previously able to work around thanks to batches running in their own forked environment.

I'm more than happy to improve upon that process if there's a better way - it's just that there's unfortunately no easy way to differentiate between multiple copies of the client open on the same system. Attempting to run multiple tests in parallel (via UFT) on the same machine causes one or more of the involved tests to crash with script errors (as in an actual script error popup message from Windows).

from serenity-cucumber-starter.

I've been trying to make things works using threads, but I can't seem to find any way to make UFT cooperate... is there no way to make Serenity or Cucumber run the different batches in their own Runtimes, rather than as a bunch of threads sharing the same runtime?

from serenity-cucumber-starter.