| Table of Contents |
|---|
...
- a directory with multiple .feature files (Run all features in)
- a .feature file (Run Feature)
- a Feature: statement (Run Feature)
- a Scenario: statement (Run Scenario)
| Warning | ||
|---|---|---|
Both IntelliJ 13 has the problem that the and 14 have problems with correctly prefilling the glue property of a run configuration is not prefilled with the correct packages (when automatically creating a run configuration). It only prefills the package containing your custom steps. If that is the case you should manually add when you are executing a scenario from the UI. You can always modify a run configuration after it has been generated, however the easiest solution is to add the correct glue (usually com.foreach.cuke) to the glue propertydefault run configuration for Cucumber Java.
|
...
Add the following step: Then pause. Then a dialogue box with an OK button appears, the scenario will continue to run after pressing OK.
Please note that sometimes the diaologbox does not appear . Pressing alt-tab, you should be able to locate it.
| Warning |
|---|
The pause step will continue to wait forever unless you click OK, so this is only useful for temporary use. On a build server, the system property = nopause must be true in order to avoid that the execution is paused. |
...
define nopause system property -Dnopause=true
>>This will ensure that any pause steps are skipped and the build does not hang forever..
- define environment with the -Denvironment system property
- all test reports are in the target/cucumber directory
- the xml file is JUnit xml foraat
- the pretty-html-reports directory is useful to link to builds as artifact/
...