Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion docs/deep-dive-into-hyperexecute-yaml.md
Original file line number Diff line number Diff line change
Expand Up @@ -1309,7 +1309,6 @@ The `afterEachScenario` flag is used to define tasks that should be executed aft
afterEachScenario:
- echo "Running a script"
- pwsh run.test
- bash script.sh
```

***
Expand Down
2 changes: 1 addition & 1 deletion docs/hyperexecute-yaml-parameters.md
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ The **HyperExecute YAML** file serves as the foundational component for test exe
| [afterAll](/support/docs/deep-dive-into-hyperexecute-yaml/#afterall) | Map |It is used to run commands after the job has finished. |
| [project](/support/docs/deep-dive-into-hyperexecute-yaml/#project) | String | Segregate data at a project/repo level |
| [slackChannel](/support/docs/deep-dive-into-hyperexecute-yaml/#slackchannel) | String | Allows you to receive notifications of your Job updates directly in your preferred Slack channel. |
| [afterEachScenario](/support/docs/deep-dive-into-hyperexecute-yaml/#aftereachscenario) | | |
| [afterEachScenario](/support/docs/deep-dive-into-hyperexecute-yaml/#aftereachscenario) | List of Strings | Allows you to trigger your define tasks after each test scenario. |

<nav aria-label="breadcrumbs">
<ul className="breadcrumbs">
Expand Down
Loading