diff --git a/assets/images/kane-ai/features/schedule-tests/1.png b/assets/images/kane-ai/features/schedule-tests/1.png new file mode 100644 index 000000000..6ed492674 Binary files /dev/null and b/assets/images/kane-ai/features/schedule-tests/1.png differ diff --git a/assets/images/kane-ai/features/schedule-tests/2.png b/assets/images/kane-ai/features/schedule-tests/2.png new file mode 100644 index 000000000..f95181bc2 Binary files /dev/null and b/assets/images/kane-ai/features/schedule-tests/2.png differ diff --git a/assets/images/kane-ai/features/schedule-tests/3.png b/assets/images/kane-ai/features/schedule-tests/3.png new file mode 100644 index 000000000..d57e4310b Binary files /dev/null and b/assets/images/kane-ai/features/schedule-tests/3.png differ diff --git a/assets/images/kane-ai/features/schedule-tests/4.png b/assets/images/kane-ai/features/schedule-tests/4.png new file mode 100644 index 000000000..1d08f7bd2 Binary files /dev/null and b/assets/images/kane-ai/features/schedule-tests/4.png differ diff --git a/assets/images/kane-ai/features/schedule-tests/5.png b/assets/images/kane-ai/features/schedule-tests/5.png new file mode 100644 index 000000000..a955a24b3 Binary files /dev/null and b/assets/images/kane-ai/features/schedule-tests/5.png differ diff --git a/assets/images/kane-ai/features/schedule-tests/6.png b/assets/images/kane-ai/features/schedule-tests/6.png new file mode 100644 index 000000000..b2bd90c72 Binary files /dev/null and b/assets/images/kane-ai/features/schedule-tests/6.png differ diff --git a/assets/images/kane-ai/features/schedule-tests/output.mp4 b/assets/images/kane-ai/features/schedule-tests/output.mp4 new file mode 100644 index 000000000..fd389e164 Binary files /dev/null and b/assets/images/kane-ai/features/schedule-tests/output.mp4 differ diff --git a/docs/hyperexecute-yaml-parameters.md b/docs/hyperexecute-yaml-parameters.md index e61525cee..ed698eadd 100644 --- a/docs/hyperexecute-yaml-parameters.md +++ b/docs/hyperexecute-yaml-parameters.md @@ -162,7 +162,6 @@ The **HyperExecute YAML** file serves as the foundational component for test exe | [postDirectives](/support/docs/deep-dive-into-hyperexecute-yaml/#postdirectives) | Map |Similar to post with option to retry. | | [alwaysRunPostSteps](/support/docs/deep-dive-into-hyperexecute-yaml/#alwaysrunpoststeps) | Boolean | Execute the Post Steps in every scenario case | | [cacheTestURL](/support/docs/deep-dive-into-hyperexecute-yaml/#cachetesturl) | Boolean |It enables users to cache static test files. | - | [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) | List of Strings | Allows you to trigger your define tasks after each test scenario. | diff --git a/docs/kaneai-scheduled-test-runs.md b/docs/kaneai-scheduled-test-runs.md new file mode 100644 index 000000000..f0b11939a --- /dev/null +++ b/docs/kaneai-scheduled-test-runs.md @@ -0,0 +1,70 @@ +--- +id: kaneai-scheduled-test-runs +title: Scheduled Test Runs +hide_title: false +sidebar_label: Scheduled Test Runs +description: This documentation will help you to understand how to create a scheduled test runs via KaneAI +keywords: +- users management lambdatest +- manage user +url: https://www.lambdatest.com/support/docs/kaneai-test-manager-access-management/ +site_name: LambdaTest +slug: kaneai-scheduled-test-runs/ +--- + + +In this documentation, you will learn how to create a scheduled test run using pre-existing test runs. This involves navigating through your project, selecting test configurations, and setting up recurring schedules to automate test executions at specified times. + +**Step 1:** Navigate to **Test Manager** >> select your desired project >> **Test Runs** section. + +testing + +**Step 2:** Here, you will see the details of your existing test runs. To create a schedule, click on the three dots next to a test run and select **Create Schedule**. Alternatively, you can go to the **Scheduled runs** section to view all existing schedules. If you don't have any existing schedule, click on **Create a Scheduled Run** button to create a scheduled run. + +> Test Runs must be created before creating a test run schedule. + +testing + +**Step 3:** Provide the details related to the test you want to schedule, like **Schedule Name**, select existing test run you want to schedule, and configure the date and time details. + +testing + +**Step 4:** After making your selections, click **Next** to review a summary of the schedule, including the scheduled date and time. + +testing + +**Step 5:** In the **Build Parameters** box, you can define your desired concurrency for the tests. Click on the **Advanced Configurations** button to configure settings like network logs, console settings, or accessibility testing. If necessary, [replace URL settings](/support/docs/kaneai-dynamic-url-replacement/). Finally, click **Schedule Test Run** to create a recurring schedule. + +testing + +**Step 6:** Click on any existing schedule to view detailed information, including a summary of test outcomes, passed and failed cases, and their respective instances. This helps in easily reviewing and proceeding with the tests. + +testing + +## Video Explanation + + diff --git a/sidebars.js b/sidebars.js index 4a59557a3..52071f229 100644 --- a/sidebars.js +++ b/sidebars.js @@ -1125,7 +1125,8 @@ module.exports = { "kaneai-modules-versions-and-enhancement", "kane-ai-assertions", "kaneai-dynamic-url-replacement", - "kaneai-chrome-options" + "kaneai-chrome-options", + "kaneai-scheduled-test-runs" ], }, {