You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an exception is thrown during the procedure of any step,
501
501
the <<Step Procedure>> *fails fast for that step*.
502
-
However, the execution of next steps won't halt by default.
502
+
However, the execution of next *steps won't halt by default*.
503
503
You can configure this behavior to *fail-fast* using the below Configuration options:
504
504
505
-
* `haltOnAnyFailure` — This defaults to `false`. If set to `true`, the execution of steps fails-fast when it encounters a failure. This also halts if there is a HTTP error response
505
+
* `haltOnAnyFailure` — This defaults to `false`. If set to `true`, the execution of steps fails-fast when it encounters a failure. This also halts if there is an HTTP error response
506
506
* `haltOnFailureOfTypeExcept` — You may configure to Fail-fast only for a specific Failure type by providing an `ExeType`. Along with it, you may provide a `PostTxnStepPick` which is used to check if a Step can be ignored for that specific failure type or halt the execution of next steps
507
507
508
508
These Configuration options, as their names suggest,
@@ -515,6 +515,13 @@ bundled with ReṼoman under link:{sourcedir}/com/salesforce/revoman/input/confi
515
515
e.g `withName`,
516
516
`inFolder` etc. You can write a custom predicate of your own too.
517
517
518
+
==== Compose Modular Executions
519
+
520
+
* You don't have to squash all your steps into one mega collection. Instead, you can break them into easy-to-manage modular collections. `ReVoman.revUp()` accepts a list of collection paths through `templatePaths()`
521
+
* But that doesn't mean you have to execute all these templates in one-go. You can make multiple `ReVoman.revUp()` calls for different collections.
522
+
* If you wish to compose these executions in a specific order, you can use the `revUp()` overload which accepts a vararg `Kick` configs.
523
+
** You can also achieve the same yourself, by adding the previous execution's `mutableEnv` to the current execution using the `dynamicEnvironment` parameter. This also comes in handy when you wish to execute a common step (e.g. `UserSetup`) inside a Test setup method and use that environment for all the tests.
524
+
518
525
[#_pre_step_and_post_step_hooks]
519
526
=== Pre-Step and Post-Step Hooks
520
527
@@ -641,13 +648,6 @@ test from link:{testdir}/com/salesforce/revoman/output/postman/PostmanEnvironmen
641
648
642
649
Each StepReport also has a `pmEnvSnapshot` to assert if a step has executed as expected and compare snapshots from different steps to examine the execution progress.
643
650
644
-
=== Compose Modular Executions
645
-
646
-
* You don't have to squash all your steps into one mega collection. Instead, you can break them into easy-to-manage modular collections. `ReVoman.revUp()` accepts a list of collection paths through `templatePaths()`
647
-
* But that doesn't mean you have to execute all these templates in one-go. You can make multiple `ReVoman.revUp()` calls for different collections.
648
-
* If you wish to compose these executions in a specific order, you can use the `revUp()` overload which accepts a vararg `Kick` configs.
649
-
** You can also achieve the same yourself, by adding the previous execution's `mutableEnv` to the current execution using the `dynamicEnvironment` parameter. This also comes in handy when you wish to execute a common step (e.g. `UserSetup`) inside a Test setup method and use that environment for all the tests.
"raw": "{\n\"name\": \"{{$randomProduct}}\", // Dynamic variable\n\"data\": {\n\"year\": {{$currentYear}}, // Variable set via Pre-req\n\"price\": {{$randomPrice}} // Variable set via Pre-req\n }\n}",
0 commit comments