2

When trying to run various features in a kind of nested manner, it seems to me that in certain setup it does not respect / execute parallel execution information correct.

Example of features structure and how they are orchestrated

    1. orchestration-main (This runs the 2 nested features serial
      1. orchestration-parallel-setup (This runs the nested feature 3 times in parallel)
        1. orchestration-parallel-setup-single (This has only serial scenarios)
      1. orchestration-parallel-tests (This runs some scenarios inside in parallel)

Now it looks like if I call 2 and 4 all works fine. However, when I call 1 it looks like as this is defined as serial it has the effect that on all nested features parallel execution instruction is ignored. Is this kind of setup not supposed to work, or am I missing something here?

Reproducer

https://github.com/romanpierson/karate-playground

Ken White
  • 123,280
  • 14
  • 225
  • 444
Roman Pierson
  • 23
  • 3

1 Answers1

1

Yes if a feature calls other features, those calls will not be run in parallel.

Peter Thomas
  • 54,465
  • 21
  • 84
  • 248
  • Thanks for confirming Thomas. Just out of curiosity, is there a specific reason this behavior is not supported? Or would you think of any way I could achieve this way of orchestration? The background to have such requirement would be to be able to run setups in parallel whereas each setup flow must be sequential. Also had a look at @setup but I see this will also not solve the issue. – Roman Pierson Mar 29 '23 at 21:18
  • @RomanPierson you can see if this answers some of your questions (use a `Scenario Outline`) https://stackoverflow.com/a/60387907/143475 - else this is a hard engineering problem and you are most welcome to look at the source and contribute improvements ;) – Peter Thomas Mar 30 '23 at 01:29