As an alternative to setting a breakpoint, that would stop the test suite and keep Jenkins and browser running for manual investigation.
There is an environment variable INTERACTIVE=true that, when provided, will pause the suite whenever a test fails/throws exception.
You can also add a call to InteractiveConsole.execute(this) in the code to stop the execution and debug in interactive groovy console.
Test harness keeps track of test diagnostic information in /target/diagnostics/<TESTNAME> directory.
For every reported file there is a JUnit Attachments marker line
printed in order to attach the diagnostic information to the test result when run in Jenkins.
All executed tests are screen recorded by default, but only videos of failing tests are persited to the target directory.
By default, each video file is named with the fully qualified test class name, minus sign (-) and the test method name.
You can configure what is persisted by using an environment variable or a Java system property called RECORDER.
Possible values are:
- off
- failuresOnly
- always
The Java system property takes precedence over environment variable.