0

When we run cucumber tests on forked JVM processes, each test is isolated pretty much immediately, so if we try to use any sort of @before or @after it will run on every single jvm instance, and yes we could setup here, it will be executed on every process pointlessly...

How can we get in before the forked JVM processes and execute a single method even to validate the test run before proceeding etc?

The same should go for a run once after all tests on all JVM's have been executed.

Is there a simple solution for this?

symon
  • 670
  • 1
  • 7
  • 20
  • Just a guess - You can execute maven from a java file. Before this, you could do your setup stuff in the java file. How to run maven from java - https://stackoverflow.com/questions/5141788/how-to-run-maven-from-java. No idea if it will work though. – Grasshopper Mar 21 '18 at 14:40

2 Answers2

1

Answer: I ended up writing a single individual test which validated the run and did all runOnce type code, telling surefire to run this test phase before the main one so the main test only continued when validation was a pass.

other alternatives: maven plugin which I also wrote does the same kind of idea. other alternatives: get the JVM forked number from maven and set it as a system property, do some action(s) where the forked number == 1 for example and pause /sleep the other JVMs until the validation has been done, then continue (will require an external source to be updated, like a properties file with:

canContinue=0

to poll on each JVM until it is 1 to continue

symon
  • 670
  • 1
  • 7
  • 20
0

Take a look of gherkin using qaf. Where you can have different listeners including one that run before suite execution. You also can write method with @BeforeSuite annotation.

user861594
  • 5,733
  • 3
  • 29
  • 45