Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.2
-
Fix Version/s: 2.4
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Currently, scenario fail in fail-fast mode (unless the ignoreFailure flag is enabled).
A batch mode can often be useful to enable long scenario builds to run through and to be have a summary batch failure at the end of the execution.
Batch mode becomes more useful (if coupled with ignoreFailure) when the user want to generate a full report of scenarios run, including any failures.
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | JBEHAVE-165.patch [ 43280 ] |
Mauro Talevi
made changes -
| Fix Version/s | 2.4 [ 15664 ] | |
| Fix Version/s | 2.3 [ 14941 ] |
Mauro Talevi
made changes -
| Summary | Enable scenarios to run in fail-batch mode | Allow scenarios to run in batch mode |
| Description |
Currently, scenario fail in fail-fast mode (unless the ignoreFailure flag is enabled). A fail-batch mode can often be useful to enable long scenario builds to run through and to be have a summary batch failure at the end of the execution. An easy way to implement this is at ScenarioRunnerMojo/Task level - but more and more there seems to be a more structured abstraction for running scenarios, so as to avoid duplication of very similar code. Possibly use the Monitor pattern to abstract logging mechanisms of Ant and Maven. |
Currently, scenario fail in fail-fast mode (unless the ignoreFailure flag is enabled). A batch mode can often be useful to enable long scenario builds to run through and to be have a summary batch failure at the end of the execution. Batch mode becomes more useful (if coupled with ignoreFailure) when the user want to generate a full report of scenarios run, including any failures. |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Simplest patch to satisfy this requirement at Mojo/Task level.