From a488a4aed3f9f14a85692ab3bf2b6391f12c7159 Mon Sep 17 00:00:00 2001 From: amanchopra1905 Date: Fri, 28 Mar 2025 16:19:17 +0530 Subject: [PATCH] updated the note for captureScreenRecordingForScenarios flag --- docs/deep-dive-into-hyperexecute-yaml.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/deep-dive-into-hyperexecute-yaml.md b/docs/deep-dive-into-hyperexecute-yaml.md index 9214ee8dd..0e8f41155 100644 --- a/docs/deep-dive-into-hyperexecute-yaml.md +++ b/docs/deep-dive-into-hyperexecute-yaml.md @@ -733,6 +733,10 @@ This can be majorly used for non selenium based tests to have the recorded video captureScreenRecordingForScenarios: true ``` +:::warning info +To avoid test failures, ensure the `video` capability is `false` before enabling the `captureScreenRecordingForScenarios` flag in your YAML file. If both `video` capability and `captureScreenRecordingForScenarios` flag is set to `true` simultaneously, the tests will fail. To prevent this conflict, always pass the capability `video: false` in your tests. +::: + *** ### `skipArtifactStageIfNoTest`