})
-2. On the **Organization Management** page, under the ORGANIZATION NAME box, concurrency limits will be displayed for the selected data center. You can also view the **PEAK VM CONCURRENCY** and **VM TESTS BY DAY** for the organization.
-
-})
+2. On the **Organization Management** page, under the ORGANIZATION NAME box, concurrency limits will be displayed for the selected data center.
3. To view the limits for another data center, in the upper-right corner of the window, click the **DATA CENTER** dropdown and select the relevant data center.
@@ -28,11 +26,16 @@ If you are an org admin, you can view your organization's concurrency limits:
})
-For more information about usage, see [Viewing and Exporting Usage Data](/basics/acct-team-mgmt/viewing-exporting-usage-data/).
+For more usage information, see [Viewing and Exporting Usage Data](/basics/acct-team-mgmt/viewing-exporting-usage-data/).
+
+5. To allocate concurrency to teams, click on the team name to open the Teams tab.
+
+6. Under the Teams tab, Enter **Team VM Concurrency** and click on Update.
-## How Concurrency Limits Work
-Through Sauce Labs, organization admins set the total concurrency of their organization's account. When setting the concurrency limit for a team, be mindful that team members share the concurrency limit of the team. If a team exceeds its concurrency limit, any additional tests will be queued (see [Queueing Tests](#queueing-tests) for more information).
+## How Concurrency Allocation Works
+
+Through Sauce Labs, organization admins set the total concurrency of their organization's account. When setting the concurrency limit for a team, be mindful that team members share the concurrency limit of the team. If a team exceeds its concurrency limit, any additional tests will be queued. Be informed that queuing will be disabled from March 1st, 2024.
#### Example - Org Limits
@@ -42,15 +45,7 @@ When Team A is using all 250 concurrency slots, that only leaves 250 of the orga
#### Example - Team Limits
-An org admin allocates 100 VMs to Team A, which has five members. Since the members of a team share the team's VM limit, the number of concurrent tests being run by the five team members cannot exceed 100. However, concurrency limits cannot be set at the user level, so User A could be running 20 tests, while user B is running 50 tests, and users C, D, and E are running 10 tests each. Or User A could be running 100 tests while Users B, C, D, and E are not running any tests.
-
-## Queueing Tests
-
-As tests complete, queued tests are allocated to concurrency slots in the order they were queued.
-
-If you run more tests at once than your concurrency allows (e.g., you have a concurrency of 100 but send 200 tests at once), the extra tests will be queued and run as the first tests finish. A test is only allowed to remain in the queue for 10 minutes. If it has not been moved out of the queue before 10 minutes elapse, or if too many tests are already queued, the test is removed from the queue and not run at all.
-
-Queuing is intended to deal with small mistakes in concurrency management. Sauce Labs does not recommend queuing tests intentionally.
+An organization admin allocates 100 VMs to Team A, which has five members. Since the members of a team share the team's VM limit, the number of concurrent tests being run by the five team members cannot exceed 100. However, concurrency limits cannot be set at the user level, so User A could be running 20 tests, while user B is running 50 tests, and users C, D, and E are running 10 tests each. Or User A could be running 100 tests while Users B, C, D, and E are not running any tests.
## Checking Concurrency
@@ -61,3 +56,17 @@ curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
--request GET 'https://api.us-west-1.saucelabs.com/rest/v1.2/users/run command.
+
+
### --no-color
| OPTIONAL | BOOLEAN | Sauce Orchestrate Only
+ +Tail the live log output from a running Sauce Orchestrate container. + +```bash +saucectl run --live-logs +``` + +
diff --git a/docs/visual-testing/integrations/storybook.md b/docs/visual-testing/integrations/storybook.md
index c76a4a7c38..d0a01ef05f 100644
--- a/docs/visual-testing/integrations/storybook.md
+++ b/docs/visual-testing/integrations/storybook.md
@@ -176,4 +176,4 @@ module.exports = {
```
-If you wanna configure your own devices please follow the configuration steps inside the [playwright docs](https://playwright.dev/docs/emulation#devices).
+If you'd like to configure your own devices, please follow the configuration steps inside the [playwright docs](https://playwright.dev/docs/emulation#devices).
diff --git a/docs/web-apps/automated-testing/cypress.md b/docs/web-apps/automated-testing/cypress.md
index e58ba400ee..3c9e979950 100644
--- a/docs/web-apps/automated-testing/cypress.md
+++ b/docs/web-apps/automated-testing/cypress.md
@@ -34,6 +34,18 @@ Sauce Labs supports the following test configurations for Cypress:
Supported Browsers
End of Life
})
-2. Enter the Selenium Quickstart Java Project URL (https://github.com/saucelabs-training/quickstart-selenium-java.git) and click **Clone from URL**.})
-
-})
-2. Enter the Selenium Quickstart Java Project URL (https://github.com/saucelabs-training/quickstart-selenium-java.git) and click **Clone**.})
-
-})
-
-})
-
-})
-
-Once you get to the **Test Results** page, click on your test to view its details.})
-
-})
-
-Once you get to the **Test Results** page, click on your test to view its details.
-
-})
-
-Once you get to the **Test Results** page, click on your test to view its details.
-
-})
-2. Provide the location where you downloaded the JDK. Some IDEs will detect and find the path for you, so all you have to do is select it.
})
-
-:::tip
-If you're new to IDEs, here are some tips:
-
-OpenJDK distributions
-IDEs also give you the option to download open source JDK distributions (e.g., Amazon Corretto, Oracle OpenJDK, and Eclipse Temurin) as an alternative to downloading JDK to your local machine. This works, but will only download it this specific project. If you're setting up a permanent developer environment that will be used beyond this Quickstart, you should download the JDK locally.})
-Extensions and plugins
-If your IDE recommends additional extensions and plugins for Java and Maven, such as the ones listed below, you should accept them since they may contain more dependencies needed to run a test.})
-})
-
-### Step 5: View Test Results
-
-You should see a Chrome browser window pop up and then quickly close. Your results will show a confirmation that ChromeDriver started successfully.})
-
-This concludes the test! If you're feeling ambitious, proceed to the next section to try out some additional common Selenium commands.
-
-### Extra Credit (Optional)
-
-In this exercise, you'll be running the same **SeleniumTest.java** test, but with a few more actions this time. You'll automate WebDriver to open a Chrome browser window, navigate to our [demo site](https://www.saucedemo.com), log in with a username and password, maximize the browser window, then close the browser window.
-
-1. Copy and paste the below code into the **SeleniumTest.java** test file, overwriting the previous test.
-
-```java
-package com.saucelabs.advancedselenium.saucedemo.tests;
-
-import org.openqa.selenium.By;
-import org.openqa.selenium.WebDriver;
-import org.openqa.selenium.chrome.ChromeDriver;
-
-public class Hello {
-
- public static void main(String[] args) {
- // Lets WebDriverManager handle drivers
- WebDriverManager.chromedriver().setup();
- // Starts session (opens browser)
- RemoteWebDriver driver = new ChromeDriver();
-
- // Opens browser with desired URL
- driver.get("https://www.saucedemo.com");
- // Inputs standard_user in username field.
- driver.findElement(By.id("user-name")).sendKeys("standard_user");
- // Inputs secret_sauce in password field
- driver.findElement(By.id("password")).sendKeys("secret_sauce");
-
- // Clicks the Login button
- driver.findElement(By.id("login-button")).click();
-
- // maximizes browser window
- driver.manage().window().maximize();
-
- // Closes browser
- driver.quit();
- }
-}
-```
-
-See [Finder Methods](/web-apps/automated-testing/selenium/#finder-methods) to learn about locating id names and other webpage elements. 2. Save your changes. 3. Run revised test.
-
-
+For additional guidance on setting up Selenium tests, please refer to our [Getting Started with Selenium guide](https://app.saucelabs.com/getting-started/guides/selenium). This guide offers step-by-step instructions to help you begin your testing journey.
## More Information
diff --git a/docs/web-apps/automated-testing/testcafe.md b/docs/web-apps/automated-testing/testcafe.md
index b591250246..88b98f3a56 100644
--- a/docs/web-apps/automated-testing/testcafe.md
+++ b/docs/web-apps/automated-testing/testcafe.md
@@ -34,6 +34,23 @@ Sauce Labs supports the following test configurations for TestCafe: