-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated the following docs as per new UI (#321)
- Loading branch information
1 parent
82884a1
commit 95812cc
Showing
3 changed files
with
159 additions
and
72 deletions.
There are no files selected for viewing
77 changes: 57 additions & 20 deletions
77
src/pages/docs/test-management/test-plans/distributed-testing.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,51 +1,88 @@ | ||
| --- | ||
| title: "Distributed testing" | ||
| title: "Distributed Testing" | ||
| page_title: "Distributed Testing in Testsigma" | ||
| metadesc: "Improve your testing efficiency with Testsigma's distributed testing. Learn how to execute tests across multiple machines and increase test coverage quickly." | ||
| noindex: false | ||
| order: 8.27 | ||
| page_id: "Distributed Testing " | ||
| page_id: "Distributed Testing" | ||
| warning: false | ||
| contextual_links: | ||
| - type: section | ||
| name: "Contents" | ||
| name: "Contents" | ||
| - type: link | ||
| name: "Steps to enable distributed testing" | ||
| name: "Prerequisites" | ||
| url: "#prerequisites" | ||
| - type: link | ||
| name: "Steps to Create Distributed Testing" | ||
| url: "#steps-to-enable-distributed-testing" | ||
| --- | ||
|
|
||
|
|
||
| --- | ||
|
|
||
|
|
||
| Distributed testing means that a test scenario is segmented into several parts, and each of them is performed on a separate machine, either sequentially or in parallel. It also suggests that the test parts interact with each other during a test run, which makes them coordinated and synchronized. | ||
|
|
||
| This type of testing is generally used to test distributed software — systems with components that run on different machines and interact with each other, such as a client-server system or an internet-based application web or intranet sites, with significant functional units running in multiple locations. | ||
|
|
||
| The goal of distributed testing is to know how different components of the system interact with each other. While multiple computers will run simultaneously during the test, each one will be running a different application component and playing a different role. | ||
|
|
||
| Distributed testing is achieved in Testsigma by splitting up test plan execution across multiple machines. To do this, Testsigma lets you select different test suites for each selected test machine, where each test suite encompasses one or more components of the application. | ||
|
|
||
| --- | ||
|
|
||
| *Distributed testing* means that a test scenario is segmented into several parts and each of them is performed on a separate machine either sequentially or in parallel. It also suggests that the test parts interact with each other during a test run which make them coordinated and synchronized. | ||
|
|
||
| This type of testing is generally used to test distributed software — systems with | ||
| components which run on different machines, and interact with each other, | ||
| such as a client-server system, or an Internet-based application web or intranet sites, with major | ||
| functional units running in multiple locations. | ||
| ## **Prerequisites** | ||
|
|
||
| The goal of distributed testing is to know how different components of the system interact with each other. While multiple computers will be running simultaneously during the test, each | ||
| one will be running a different component of the application, and will be | ||
| playing a different role. | ||
| - You should know [how to create a test suite](https://testsigma.com/docs/test-management/test-suites/overview/#creating-a-test-suite). | ||
|
|
||
| Distributed testing is achieved in Testsigma by splitting up test plan execution across multiple machines. To do this, Testsigma lets you select different test suites for each selected test machine where each test suite encompasses one or more component of the application. | ||
| - You should know [how to create a test plan](https://testsigma.com/docs/test-management/test-plans/overview/#steps-to-create-a-test-plan). | ||
|
|
||
| <br> | ||
| - You should know [how to manage test machines](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/). | ||
|
|
||
| --- | ||
|
|
||
| ## **Steps to enable distributed testing** | ||
|
|
||
| 1. Navigate to **Test Plans** and click on **Create Test Plan**. | ||
|
|
||
|  | ||
|
|
||
| 1. Navigate to **Test Machines & Suites Selection** under the **Create test plan** form. *If you are not familiar with creating a test plan, refer to [add, edit,delete a test plan](https://testsigma.com/docs/test-management/test-plans/overview/)*. | ||
| 2. On the **Create Test Plan** page, select **Custom test plan** from **Test Plan Type**. | ||
|
|
||
| 2. Under the **Test machines & suites selection** tab,select the test suite for which you want to add the test machine for test execution. *For more information refer to [adding test suites](https://testsigma.com/docs/test-management/test-plans/manage-test-suites/)* | ||
|  | ||
|
|
||
| 3. Once you have selected the test suites, select the test machines to run the coressponding test suite. *For more information refer to [add test machines](https://testsigma.com/docs/test-management/test-plans/manage-test-machines/)*. | ||
| [[info | Note:]] | ||
| |To enable distributed testing you have to select different test suites for different test machines. | ||
| 3. Click on **Add Test Suites & Link Machine Profiles**. | ||
|
|
||
| See the below GIF to understand the workflow to enable distributed testing: | ||
|  | ||
|
|
||
| 4. Click on **Add Test Suites**. | ||
|
|
||
|  | ||
|
|
||
| 5. Select test suites and click on **Add to Plan**. | ||
|
|
||
|  | ||
|
|
||
| 6. Click on **Test Machine** to add test machines to run the test suite. | ||
|
|
||
|  | ||
|
|
||
| 7. On **Select test machine profiles** overlay, select test machines and click on **Save selections**. | ||
|
|
||
|  | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | For distributed testing, you must select different test suites for different test machines. You can hover over the test suite and click on the test machine corresponding to it to add a different test machine to the test suite. | ||
|
|
||
| 8. Go to **Test Plan Settings** and click on **Create**. | ||
|  | ||
|
|
||
|
|
||
| <br> | ||
|
|
||
| Here’s a quick GIF demonstrating how to create distributed testing in Testsigma. | ||
|
|
||
|  | ||
|
|
||
| --- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
52 changes: 38 additions & 14 deletions
52
...pages/docs/troubleshooting/mobile-apps/test-execution-queued-for-a-long-time.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,29 +1,53 @@ | ||
| --- | ||
| title: "Test execution state is Queued for a long time" | ||
| metadesc: "Understand why your test execution state may be stuck in Queued state for an extended period | Know the possible reasons and solutions to resolve the issue" | ||
| title: "Test Execution State is Queued for a Long Time" | ||
| metadesc: "Understand why your test execution state may be stuck in Queued state for an extended period | Know the possible reasons why your test execution is Queued" | ||
| noindex: false | ||
| order: 23.6 | ||
| page_id: "Troubleshooting “Test execution state is Queued for a long time” error" | ||
| warning: false | ||
| contextual_links: | ||
| - type: section | ||
| name: "Contents" | ||
| - type: link | ||
| name: "Steps to Troubleshoot the Issue" | ||
| url: "#steps-to-troubleshoot-the-issue" | ||
| --- | ||
|
|
||
| --- | ||
|
|
||
|
|
||
| If the execution status for your tests has been in the state **Queued** for a long time then, one of the possible reasons is that the number of total parallel runs allowed on your license are already in use. | ||
|
|
||
|
|
||
| --- | ||
|
|
||
| ## **Steps to Troubleshoot the Issue** | ||
|
|
||
| 1. On **Dashboard**, click on **Usage details**. | ||
|
|
||
|  | ||
|
|
||
| 2. Check the number of **Parallel Tests**. | ||
|
|
||
|  | ||
|
|
||
|
|
||
| Here, we have a license for 3 parallel executions & 3 allowed queues. We can set up a maximum of 3 test runs to run in parallel, which means executing up to 3 tests simultaneously. In addition to the 3 tests running in parallel, you can have up to 3 tests in the queue. The queued tests will execute once the ongoing parallel executions are complete. | ||
|
|
||
| In the above example, we have **Parallel Tests 2/3**, which means 2 tests are running in parallel, and 3 is the number of parallel runs allowed at a moment. | ||
|
|
||
| 3. Suppose the number of parallel runs is equal to the number of parallel licenses for your Testsigma account. In that case, the tests in the queue will remain in the same status until the parallel test runs are completed. | ||
|
|
||
| If the execution status for your tests has been in the state "Queued" for a long time then, one of the possible reasons is that the number of total parallel runs allowed on your license are already in use. To check if this is the issue, follow below steps: | ||
| 1. Click on the "Usage Details" button on the Left Navigation Menu, as also highlighted in the screenshot below: | ||
|
|
||
|  | ||
| **You can take the following actions to fix the issue:** | ||
|
|
||
| 2. Check the number of Parallel Tests. | ||
| - You can wait for other tests to complete execution. | ||
|
|
||
|  | ||
| - You can connect with Testsigma support (**support@testsigma.com**) to increase the number of parallel runs allowed on your license. | ||
|
|
||
| In this screenshot, 3/5 means - 3 tests are running in parallel and 5 is the number of parallel runs allowed at a moment. | ||
| <br> | ||
|
|
||
| 3. If the number of parallel runs is equal to the number of parallel licenses for your Testsigma account then you can take following actions to fix the issue: | ||
| i. You can wait for other tests to complete execution. | ||
| ii. You can talk to Testsigma support to increase the number of parallel runs allowed on your license. | ||
| iii. You can click on the name of the test displayed in the Usage Details window and check its details. This can only be done if you have access to the test case. | ||
|  | ||
| Here’s the GIF demonstrating how to check the usage details in Testsigma. | ||
|  | ||
|
|
||
| iv. If you have appropriate rights, you can also stop the execution of one of the test cases by clicking on the corresponding stop button. | ||
| --- |