diff --git a/assets/images/milestones/1.png b/assets/images/milestones/1.png new file mode 100644 index 000000000..ab6ffb74b Binary files /dev/null and b/assets/images/milestones/1.png differ diff --git a/assets/images/milestones/2.png b/assets/images/milestones/2.png new file mode 100644 index 000000000..75745eef3 Binary files /dev/null and b/assets/images/milestones/2.png differ diff --git a/assets/images/milestones/3.png b/assets/images/milestones/3.png new file mode 100644 index 000000000..7bca4aad2 Binary files /dev/null and b/assets/images/milestones/3.png differ diff --git a/assets/images/milestones/4.png b/assets/images/milestones/4.png new file mode 100644 index 000000000..8e6d9255e Binary files /dev/null and b/assets/images/milestones/4.png differ diff --git a/assets/images/milestones/5.png b/assets/images/milestones/5.png new file mode 100644 index 000000000..44ca725a6 Binary files /dev/null and b/assets/images/milestones/5.png differ diff --git a/assets/images/milestones/6.png b/assets/images/milestones/6.png new file mode 100644 index 000000000..8a9c8a778 Binary files /dev/null and b/assets/images/milestones/6.png differ diff --git a/assets/images/milestones/output.mp4 b/assets/images/milestones/output.mp4 new file mode 100644 index 000000000..010b54595 Binary files /dev/null and b/assets/images/milestones/output.mp4 differ diff --git a/assets/images/mobile-app-testing/add-bulk-details.webp b/assets/images/mobile-app-testing/add-bulk-details.webp deleted file mode 100644 index 4caf0a966..000000000 Binary files a/assets/images/mobile-app-testing/add-bulk-details.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/add-details.webp b/assets/images/mobile-app-testing/add-details.webp deleted file mode 100644 index 4fc7fdac5..000000000 Binary files a/assets/images/mobile-app-testing/add-details.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/archive-build.webp b/assets/images/mobile-app-testing/archive-build.webp deleted file mode 100644 index a7ba64aee..000000000 Binary files a/assets/images/mobile-app-testing/archive-build.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/assign-variables.webp b/assets/images/mobile-app-testing/assign-variables.webp deleted file mode 100644 index 105023ce1..000000000 Binary files a/assets/images/mobile-app-testing/assign-variables.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/browse-test-cases.webp b/assets/images/mobile-app-testing/browse-test-cases.webp deleted file mode 100644 index 8ea007711..000000000 Binary files a/assets/images/mobile-app-testing/browse-test-cases.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-creator.webp b/assets/images/mobile-app-testing/build-creator.webp deleted file mode 100644 index 2cdb2d7ba..000000000 Binary files a/assets/images/mobile-app-testing/build-creator.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-history-options.webp b/assets/images/mobile-app-testing/build-history-options.webp deleted file mode 100644 index a59ccfbf1..000000000 Binary files a/assets/images/mobile-app-testing/build-history-options.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-history.webp b/assets/images/mobile-app-testing/build-history.webp deleted file mode 100644 index 56d74d385..000000000 Binary files a/assets/images/mobile-app-testing/build-history.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-information.webp b/assets/images/mobile-app-testing/build-information.webp deleted file mode 100644 index adfbe2e1d..000000000 Binary files a/assets/images/mobile-app-testing/build-information.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-is-created.webp b/assets/images/mobile-app-testing/build-is-created.webp deleted file mode 100644 index 6ca468c12..000000000 Binary files a/assets/images/mobile-app-testing/build-is-created.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-section-options.webp b/assets/images/mobile-app-testing/build-section-options.webp deleted file mode 100644 index ec3f36275..000000000 Binary files a/assets/images/mobile-app-testing/build-section-options.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-section.webp b/assets/images/mobile-app-testing/build-section.webp deleted file mode 100644 index 1bb42856c..000000000 Binary files a/assets/images/mobile-app-testing/build-section.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-status.webp b/assets/images/mobile-app-testing/build-status.webp deleted file mode 100644 index 62342e61f..000000000 Binary files a/assets/images/mobile-app-testing/build-status.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/build-tags.webp b/assets/images/mobile-app-testing/build-tags.webp deleted file mode 100644 index 5e1348ff2..000000000 Binary files a/assets/images/mobile-app-testing/build-tags.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/capture-screenshots.webp b/assets/images/mobile-app-testing/capture-screenshots.webp deleted file mode 100644 index 3c191b8e3..000000000 Binary files a/assets/images/mobile-app-testing/capture-screenshots.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/click-on-create-test-plan.webp b/assets/images/mobile-app-testing/click-on-create-test-plan.webp deleted file mode 100644 index 5e35b2676..000000000 Binary files a/assets/images/mobile-app-testing/click-on-create-test-plan.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/create-build.webp b/assets/images/mobile-app-testing/create-build.webp deleted file mode 100644 index 5f0ef7416..000000000 Binary files a/assets/images/mobile-app-testing/create-build.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/create-new-configuration.webp b/assets/images/mobile-app-testing/create-new-configuration.webp deleted file mode 100644 index 761ddad94..000000000 Binary files a/assets/images/mobile-app-testing/create-new-configuration.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/create-test-plan.webp b/assets/images/mobile-app-testing/create-test-plan.webp deleted file mode 100644 index c70477eb0..000000000 Binary files a/assets/images/mobile-app-testing/create-test-plan.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/detailed-test-cases-view.webp b/assets/images/mobile-app-testing/detailed-test-cases-view.webp deleted file mode 100644 index e2d2693a8..000000000 Binary files a/assets/images/mobile-app-testing/detailed-test-cases-view.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/duplicate-build.webp b/assets/images/mobile-app-testing/duplicate-build.webp deleted file mode 100644 index 8fafd7525..000000000 Binary files a/assets/images/mobile-app-testing/duplicate-build.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/edit-build.webp b/assets/images/mobile-app-testing/edit-build.webp deleted file mode 100644 index 812a46fc7..000000000 Binary files a/assets/images/mobile-app-testing/edit-build.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/expand-details.webp b/assets/images/mobile-app-testing/expand-details.webp deleted file mode 100644 index f858b4f51..000000000 Binary files a/assets/images/mobile-app-testing/expand-details.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/run-build.webp b/assets/images/mobile-app-testing/run-build.webp deleted file mode 100644 index 7d2886ffd..000000000 Binary files a/assets/images/mobile-app-testing/run-build.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/run-test-case.webp b/assets/images/mobile-app-testing/run-test-case.webp deleted file mode 100644 index bc47c2fa2..000000000 Binary files a/assets/images/mobile-app-testing/run-test-case.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/select-any-test-case.webp b/assets/images/mobile-app-testing/select-any-test-case.webp deleted file mode 100644 index 28ee2ebe0..000000000 Binary files a/assets/images/mobile-app-testing/select-any-test-case.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/select-configurations.webp b/assets/images/mobile-app-testing/select-configurations.webp deleted file mode 100644 index ee56348b6..000000000 Binary files a/assets/images/mobile-app-testing/select-configurations.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/selected-test-cases.webp b/assets/images/mobile-app-testing/selected-test-cases.webp deleted file mode 100644 index 910d26f46..000000000 Binary files a/assets/images/mobile-app-testing/selected-test-cases.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/status-of-builds.webp b/assets/images/mobile-app-testing/status-of-builds.webp deleted file mode 100644 index fd611ec4e..000000000 Binary files a/assets/images/mobile-app-testing/status-of-builds.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/switch-configurations.webp b/assets/images/mobile-app-testing/switch-configurations.webp deleted file mode 100644 index c348b18d3..000000000 Binary files a/assets/images/mobile-app-testing/switch-configurations.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/test-case-status.webp b/assets/images/mobile-app-testing/test-case-status.webp deleted file mode 100644 index 3bc11856d..000000000 Binary files a/assets/images/mobile-app-testing/test-case-status.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/test-plan-creation-workflow.webp b/assets/images/mobile-app-testing/test-plan-creation-workflow.webp deleted file mode 100644 index e19d3fddd..000000000 Binary files a/assets/images/mobile-app-testing/test-plan-creation-workflow.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/test-plans-option.webp b/assets/images/mobile-app-testing/test-plans-option.webp deleted file mode 100644 index 394e5542a..000000000 Binary files a/assets/images/mobile-app-testing/test-plans-option.webp and /dev/null differ diff --git a/assets/images/mobile-app-testing/test-step-execution-summary.webp b/assets/images/mobile-app-testing/test-step-execution-summary.webp deleted file mode 100644 index eec32b809..000000000 Binary files a/assets/images/mobile-app-testing/test-step-execution-summary.webp and /dev/null differ diff --git a/assets/images/test-run/1.png b/assets/images/test-run/1.png new file mode 100644 index 000000000..320754e19 Binary files /dev/null and b/assets/images/test-run/1.png differ diff --git a/assets/images/test-run/10.png b/assets/images/test-run/10.png new file mode 100644 index 000000000..8ec46c506 Binary files /dev/null and b/assets/images/test-run/10.png differ diff --git a/assets/images/test-run/11.png b/assets/images/test-run/11.png new file mode 100644 index 000000000..c124b80f3 Binary files /dev/null and b/assets/images/test-run/11.png differ diff --git a/assets/images/test-run/12.png b/assets/images/test-run/12.png new file mode 100644 index 000000000..64e861d00 Binary files /dev/null and b/assets/images/test-run/12.png differ diff --git a/assets/images/test-run/13.png b/assets/images/test-run/13.png new file mode 100644 index 000000000..5d7ce25fa Binary files /dev/null and b/assets/images/test-run/13.png differ diff --git a/assets/images/test-run/2.png b/assets/images/test-run/2.png new file mode 100644 index 000000000..4bc9d1fb2 Binary files /dev/null and b/assets/images/test-run/2.png differ diff --git a/assets/images/test-run/3.png b/assets/images/test-run/3.png new file mode 100644 index 000000000..965f1cbd4 Binary files /dev/null and b/assets/images/test-run/3.png differ diff --git a/assets/images/test-run/4.png b/assets/images/test-run/4.png new file mode 100644 index 000000000..3539d6ea7 Binary files /dev/null and b/assets/images/test-run/4.png differ diff --git a/assets/images/test-run/5.png b/assets/images/test-run/5.png new file mode 100644 index 000000000..7148c7d7c Binary files /dev/null and b/assets/images/test-run/5.png differ diff --git a/assets/images/test-run/6.png b/assets/images/test-run/6.png new file mode 100644 index 000000000..b9e741939 Binary files /dev/null and b/assets/images/test-run/6.png differ diff --git a/assets/images/test-run/7.png b/assets/images/test-run/7.png new file mode 100644 index 000000000..7a01e3724 Binary files /dev/null and b/assets/images/test-run/7.png differ diff --git a/assets/images/test-run/8.png b/assets/images/test-run/8.png new file mode 100644 index 000000000..b3a324a4a Binary files /dev/null and b/assets/images/test-run/8.png differ diff --git a/assets/images/test-run/9.png b/assets/images/test-run/9.png new file mode 100644 index 000000000..a36c2b231 Binary files /dev/null and b/assets/images/test-run/9.png differ diff --git a/assets/images/test-run/output.mp4 b/assets/images/test-run/output.mp4 new file mode 100644 index 000000000..8f68d8dde Binary files /dev/null and b/assets/images/test-run/output.mp4 differ diff --git a/docs/build-creation.md b/docs/build-creation.md deleted file mode 100644 index 00ff23ebd..000000000 --- a/docs/build-creation.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -id: build-creation -title: Build Creation -hide_title: true -sidebar_label: Build Creation -description: Learn build creation with LambdaTest to efficiently set up and manage builds for optimized testing and seamless project execution. -keywords: - - build creation - - builds -url: https://www.lambdatest.com/support/docs/build-creation/ -site_name: LambdaTest -slug: build-creation/ ---- - - - -# Build Creation - -Builds are instrumental in the execution and evaluation of test plans. From their creation to the assignment and attachment of test evidence, builds streamline the testing process, ensuring a comprehensive and well-documented approach to software validation. - -Creating a build in Test Manager is an important step that helps test plan from the planning stage to execution. This process involves specifying a unique build name and associating it with a set of test cases and configurations, setting the stage for a structured testing effort through a user-friendly interface. - -**Steps for Creating a Build** - -1. Create a build for the test plan by clicking the Create Build button in the test plan section. Alternatively, navigate to the builds section and click on **Create Build**. - -Real - -2. Choose the test plan that will be executed as part of this build and enter relevant information such as **Build Name**, **Tag(s)**, and select **Create**. - -Real - -3. The build is now created. Enter details to mark status for various credentials such as **Status** and **Assignee**. - -Real - - - - - - \ No newline at end of file diff --git a/docs/build-details.md b/docs/build-details.md deleted file mode 100644 index b10418e0d..000000000 --- a/docs/build-details.md +++ /dev/null @@ -1,85 +0,0 @@ ---- -id: build-details -title: Build Details -hide_title: true -sidebar_label: Build Details -description: Explore comprehensive build details on LambdaTest to enhance your testing strategy and gain deeper insights into your test executions. -keywords: - - build details - - navigating build details -url: https://www.lambdatest.com/support/docs/build-details/ -site_name: LambdaTest -slug: build-details/ ---- - - - -# Build Details - -Users can quickly review the status of testing via the builds listing interface. It offers a concise summary of the number of test cases that have passed, failed, or been skipped, providing an understanding of the state of the testing process as a whole. This aids in the identification of potential issues and successful validations. - -Users can also enhance their testing by attaching test evidence such as screenshots and videos. It provides a visual record for any specific test scenario. - -**Navigating Build Details** - -1. To view the details of a particular build, go to the **Builds** section. It provides a summary of the execution results, showing one build passed and another in progress. - -Real - -2. Click on the three dots on the right-hand side to find options to **Edit Build**, **Duplicate Build** or **Archive Build**. - -Real - -3. Select **Edit Build** to add the **Edit Name** and **Tag(s)**, then click **Update**. - -Real - -4. For duplicating, choose **Duplicate Build**, enter the **Build Name** and **Tag(s)**, and click **Create**. - -Real - -5. To archive, choose **Archive Build**, then go to the **View** toggle to see both **Active** and **Archived** builds. - -Real - - \ No newline at end of file diff --git a/docs/build-history.md b/docs/build-history.md deleted file mode 100644 index 9d2e7f0ed..000000000 --- a/docs/build-history.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -id: build-history -title: Build History -hide_title: true -sidebar_label: Build History -description: Review your test build executions with LambdaTest's Build History, streamlining your tracking for better testing outcomes and decisions. -keywords: - - build history - - build - - builds -url: https://www.lambdatest.com/support/docs/build-history/ -site_name: LambdaTest -slug: build-history/ ---- - - - -# Build History - -Test Manager provides users with the build history for each test plan. This feature showcases all the run instances of the plan, providing insights into the testing progression over time. The build history includes the status of each run instance, offering a quick and informative overview of the success or issues encountered during the testing process. - -**Navigating Build History** - -1. In the test plan section, navigate to the desired test plan and click on the Build History tab. Each entry in the **Build History** shows a test execution instance with details on when and by whom the build was created. - -Real - -2. By clicking on **Status**, filter builds based on their status such as **Passed**, **Failed**, **Skipped**, **In Progress** and **Not Started**. - -Real - -3. Builds can also be selected based on **Tags**, which helps categorize and access them more efficiently according to specific criteria. - -Real - -4. The **Creator** option allows you to select test cases based on assignee. - -Real - -5. On the right side, view the status of test cases based on their execution. - -Real - - - - - diff --git a/docs/execute-builds.md b/docs/execute-builds.md deleted file mode 100644 index 184ba9bc9..000000000 --- a/docs/execute-builds.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -id: execute-builds -title: Execute Builds -hide_title: true -sidebar_label: Execute Builds -description: Discover how to execute builds effectively using LambdaTest, optimizing your testing process for better efficiency and reliability. -keywords: - - execute builds - - steps for execution of a build -url: https://www.lambdatest.com/support/docs/execute-builds/ -site_name: LambdaTest -slug: execute-builds/ ---- - - - -# Execute Builds - -Test Manager enhances real-time testing by offering a dynamic interface that displays the step by step progress of each test case as they are executed, providing visibility and detailed insights into the testing process. - -Executing a build in Test Manager initiates the testing phase for your selected test plan, marking a crucial step towards validating the functionality and performance of your test cases by running all the associated test cases within the build based on selected configurations. - -**Steps for Execution of a Build** - -1. Click on the created build. To execute it, ensure the **Status** and **Assignee** are added, then click **Run Build** on the right side to execute all test cases at once. - -Real - -2. You can also run the test cases individually by clicking on **Run Test Case**. - -Real - -3. Upon execution, the screen redirects to the test case location based on the selected configuration. A notification box appears in the top right-hand corner. After each test step, a screenshot is automatically captured, with the option to manually capture additional screenshots. - -Real - -4. Click on **Expand details** to view the test steps for the test case. The image labeled as **Test Evidence** is captured automatically, and the **Recorded Media** displays the screenshots captured by users. - -Real - -5. The status for each test step for **test case 1** must be marked as Passed or Failed in the **Test Step Execution Summary** box along with remarks. Also mark the status as **Passed** in the top right hand side. - -Real - -6. Switch configurations to proceed with the **Next Test Case**. - -Real - -7. If not executing the test case based on its configuration, select the test case and mark its status as Passed, Failed, or Skipped. In the image below, step 1 is marked as passed, step 2 as failed, and step 3 as skipped. - -Real - -8. All selected test cases have been executed according to their configurations and assignees. Test cases 1 and 2, not executed through LambdaTest, will display a symbol indicating the same. Update the progress status in the top right corner. - -Real - -9. Click on the test case executed to have a detailed view of the **Test Steps**. - -Real - -10. The status of the number of builds **Passed**, **Failed**, **Skipped** or **Not Started** can be viewed as shown in the below image - -Real - - - \ No newline at end of file diff --git a/docs/milestone-creation-and-management.md b/docs/milestone-creation-and-management.md new file mode 100644 index 000000000..84a1f3470 --- /dev/null +++ b/docs/milestone-creation-and-management.md @@ -0,0 +1,86 @@ +--- +id: milestone-creation-and-management +title: Milestones - Creation and Management +hide_title: false +sidebar_label: Milestones +description: Check the milestones - datasets, test run and +keywords: + - milestone creation +url: https://www.lambdatest.com/support/docs/milestone-creation-and-management/ +site_name: LambdaTest +slug: milestone-creation-and-management/ +--- + + +Milestones in LambdaTest serve as a central organizational tool for grouping test runs. They are particularly useful for tracking progress related to feature releases, ensuring comprehensive oversight of associated testing activities. + +This guide provides a comprehensive walkthrough for creating and managing milestones within LambdaTest, enabling efficient organization of test runs and tracking feature releases. + +## Creating a Milestone +### Step 1: Access the Milestone Section +- Navigate to the Milestone section in the LambdaTest dashboard. +- Click **"Create Milestone**" and locate the Create Milestone button and click it to start the creation process. +Real + +### Step 2: Provide the required configurations +- Enter the following mandatory fields: + - **Milestone Name :** Provide a clear and descriptive name for the milestone. + - **Associated Test Runs:** Select or specify the test runs you want to include. + - Optional fields: + - **Description :** Add additional information about the milestone’s purpose or scope. + - **Tags :** Assign relevant tags for categorization. + - **Owner :** Designate a team member responsible for the milestone. + - **Duration :** Set the expected duration for completing the milestone. + - **Attachments :** Upload any relevant files or documentation. +Real + +### Step 3: Finalize the Milestone +- Review all entered details for accuracy. +- Click **Create Milestone** to finalize the creation. +Real + +## Managing Milestones +### Viewing Milestone Details +Once created, all milestones are listed for easy tracking. You can: +- Select a specific milestone to view its detailed information. +- Access associated test runs and other milestone attributes. +Real + +### Marking Milestones as Completed +When a milestone is finished, you can mark it as Completed: +- Navigate to the desired milestone. +- Use the Mark as Completed option to update its status. +Real + +### Viewing Completed Milestones +To review completed milestones: +- Navigate to the View Completed section in the milestone management area. +- This section provides a history of all milestones marked as complete. +Real + +## Video Explanation + \ No newline at end of file diff --git a/docs/support.md b/docs/support.md index 0d8e99d6f..1fc03dd63 100644 --- a/docs/support.md +++ b/docs/support.md @@ -200,8 +200,8 @@ import NewTag from '../src/component/newTag';

Insights Dashboard

Manual Test Cases

Automated Test Cases

-

Test Plan Creation

-

Builds

+

Test Run

+

Milestones

Jira Integration

diff --git a/docs/test-plan-creation.md b/docs/test-plan-creation.md deleted file mode 100644 index 706d695ce..000000000 --- a/docs/test-plan-creation.md +++ /dev/null @@ -1,114 +0,0 @@ ---- -id: test-plan-creation -title: Test Plan Creation -hide_title: true -sidebar_label: Test Plan Creation -description: Gain insights into effective Test Plan Creation with LambdaTest, designed to streamline your workflow. -keywords: - - test plan - - test plan creation -url: https://www.lambdatest.com/support/docs/test-plan-creation/ -site_name: LambdaTest -slug: test-plan-creation/ ---- - - - -# Test Plan Creation - -Test plans are collections of test cases which help in achieving certain test objectives by selecting and validating important test cases. By providing a structured approach to testing, test plans ensure that a particular goal or objective is tested and verified. - -The process of creating a test plan is user-friendly and intuitive. Users can seamlessly begin this process by selecting the "Test Plans" option from the repository. It provides a workflow to follow necessary steps for defining and structuring the test plan. - -**Steps for Creating a Test Plan** - -1. Under Test cases, select multiple test cases and choose the **Create Test Plan** option. - -Real - -2. Alternatively, click on the **Test Plans** dashboard and click on the toggle that says **Create Test Plan**. - -Real - -3. You will be redirected to the test plan creation workflow. Enter the **Plan Name**, **Description**, and **Tag(s)**, then select **Next** to proceed. - -Real - -4. Select **Browse Test Cases** to add additional test cases. - -Real - -5. Choose the test case of your choice from the list that appears and click on **Finish**. - -Real - -6. It is recommended to add details such as **Priority**, **Assignee** and **Configurations** for the test cases to create a build. Multiple test cases can also be added using the **Add Test Cases** option available on the top right hand side. - -Real - -7. Select all the test cases together to add bulk assignees and configurations or click on **Select Assignee** and **Select Configuration** individually. - -Real - -8. Select configurations from the list of existing configurations. You can search or filter them as well. - -Real - -9. To create a new configuration, start typing the title of the configuration as shown in the image below. - -Real - -10. Click on **Assign Variables** to select your preferred Operating Systems and Browsers. Once selected, click on **Assign & Continue** to finalize your choices. - -Real - -11. Select the **Priority**, **Assignee** and **Configuration** for the test cases, click on **Update Test Plan**. - -Real - -**NOTE:** If you choose multiple configurations for your test case, the number of entries for the test case increases by the number of configurations used. - - - - - \ No newline at end of file diff --git a/docs/test-run-creation-and-management.md b/docs/test-run-creation-and-management.md new file mode 100644 index 000000000..a636d3f3d --- /dev/null +++ b/docs/test-run-creation-and-management.md @@ -0,0 +1,130 @@ +--- +id: test-run-creation-and-management +title: Test Run - Creation and Management +hide_title: false +sidebar_label: Test Run +description: Gain insights into effective Test Run Creation with LambdaTest, designed to streamline your workflow. +keywords: + - test run + - test run creation +url: https://www.lambdatest.com/support/docs/test-run-creation-and-management/ +site_name: LambdaTest +slug: test-run-creation-and-management/ +--- + + +This guide outlines the steps required to create, configure, and manage test runs within LambdaTest's Test Manager. It provides developers and testers with a clear understanding of the process, enabling efficient test execution and organization. + +## 1. Creating a Test Run +### Step 1: Initiate a New Test Run +- Navigate to the Test Manager and click on **Create Test Run**. +- Enter a Test Run Name and an optional Description to define the purpose of the test run. + +:::tip +Use descriptive names to easily identify test runs later. +::: + +Real + +### Step 2: Add Tags +- Assign relevant Tags to categorize the test run. +- Click **Create Test Run** to proceed. + +Real + +## 2. Adding and Configuring Test Cases +### Step 3: Access the Test Cases Tab +- Upon successful creation, you will be redirected to the Test Cases tab. +- Here, you can add multiple test cases to the test run. + +Real + +### Step 4: Assign Test Cases +- Select the desired test cases from the list. +- Assign Assignees to each test case. +- Add test case configurations individually or in bulk. +> Note: Configurations allow you to define environment settings, such as browser and device combinations. + +Real + +### Step 5: Add Configurations +- Choose multiple configurations from the dropdown or create new configurations as needed. +- Apply configurations to the selected test cases. + +Real + +## 3. Saving and Managing Test Runs +### Step 6: Finalize the Test Run +- Click Save Test Run to finalize the setup. +- View the created test run and its associated test cases in the main dashboard. + +Real + +### Step 7: Bulk Update Options +- To update multiple test instances: +- Select multiple test instances. +- Use the Select Assignee and Select Status options to apply changes in bulk. + +Real + +### Step 8: Individual Test Step Management +- Within any test instance, individually update the status of each test step. +- Add remarks or actual outcomes for manual test steps. + +Real + +## 4. Enhancing Test Runs with Additional Context +### Step 9: Adding Remarks and Attachments +- Add Remarks or actual outcomes to enhance test instance execution details. + +Real + +- Attach supporting files or screenshots to the remarks for better context. + +Real + +### Step 10: Editing Test Runs +- Modify an existing test run by adding new test cases or removing unnecessary ones. +- Access the test run’s options to make edits. + +Real + +## 5. Executing and Archiving Test Runs +### Step 11: Execute on LambdaTest Cloud +- Click the Play Icon to execute test instances on the LambdaTest Cloud. +- During execution, manually update the status of test cases and test steps as needed. + +Real + +### Step 12: Duplicate or Archive Test Runs +- Use the three-dot menu on a test run to Duplicate or Archive the run. +- Archiving helps maintain a clean workspace by storing completed test runs separately. + +Real + +## Video Explanation + \ No newline at end of file diff --git a/sidebars.js b/sidebars.js index cdc8bec78..778d23ec4 100644 --- a/sidebars.js +++ b/sidebars.js @@ -1742,16 +1742,14 @@ module.exports = { ], }, { - type: "category", - collapsed: true, - label: "Test Plan", - items: ["test-plan-creation", "build-history"], + type: "doc", + label: "Test Run", + id: 'test-run-creation-and-management', }, { - type: "category", - collapsed: true, - label: "Build", - items: ["build-creation", "execute-builds", "build-details"], + type: "doc", + label: "Milestones", + id: 'milestone-creation-and-management', }, { type: "category",