afterEachScenario flag - HyperExecute

docs/deep-dive-into-hyperexecute-yaml.md

@@ -1302,6 +1302,18 @@ We can choose to run on local/remote(on HYP Vms) from the location command. Type
 
 ***
 
+### `afterEachScenario`
+The `afterEachScenario` flag is used to define tasks that should be executed after each test scenario. This can be particularly useful for cleanup activities, such as clearing cookies, resetting databases, or capturing logs, ensuring that each test scenario starts with a clean state. This flag allows you to specify a list of commands or scripts that will run sequentially after the completion of each scenario. This ensures that any necessary teardown steps are consistently applied, maintaining the integrity and isolation of your test scenarios.
+
+```yaml
+afterEachScenario:
+  - echo "Running a script"
+  - pwsh run.test
+  - bash script.sh
+```
+
+***
+
 ### `buildConfig`
 
 This is used to manage hyperlink behavior based on test status. Here's a breakdown of the parameters within buildConfig:

docs/hyperexecute-yaml-parameters.md

@@ -163,6 +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) |  | |
 
 <nav aria-label="breadcrumbs">
   <ul className="breadcrumbs">