-Dkarate.options flag disables the parallel execution in 1.4.1

[bondar-artem]

Description:
When using a flag in the command line to run tests with a -Dkarate.options, it disables the parallel execution of the tests.

Project to reproduce: https://github.com/bondar-artem/karate-parallel-issue

Steps:

1. Open project, run mvn clean test. 5 tests executed in parallel
2. Run command mvn clean test "-Dkarate.options=classpath:examples/TestParallel.feature". Tests executed in a single thread
3. Update karate to version 1.4.0, and execute command from the step 2. Tests executed in parallel.

[ptrthomas]

@bondar-artem thanks for the repro ! it would be good to confirm if -Dkarate.options=-T 5 classpath:examples/TestParallel.feature is a workaround.

I hope there are no concerns if the fix is for1.5.0 - which means Java 17 is a must.

[bondar-artem]

Thank you, Peter! Yeah looks like this workaround works!
No concerns for me about Java 17 :)

[dvargas46]

My team and I experienced this issue too. We use karate.options quite often (w/o the threads arg) to run certain tags on demand, it's really handy. Since we set the thread count on the builder config, we expect it to use that value when no override is specified on karate.options, but we see it going back to 1 instead.

I think one possible solution could be to use a boxed integer for the thread count on Main without a default value. That way we could do a simple null check when it's parsed in the Runner to see if it was a supplied option or not, similar to the other options. I can test it out sometime and create a PR if it works out.

[ptrthomas]

@dvargas46 yes please do submit a PR this - thanks for the work on the other one I will merge when I get a chance

[ptrthomas]

karate 1.5.0.RC3 including this fix is now available