Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: testcafe browser provider benefits #2950

Merged
merged 2 commits into from
Sep 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions docs/web-apps/automated-testing/testcafe/provider-plugin.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,14 @@ sidebar_label: Provider Plugin

TestCafe can also connect to Sauce Labs _remotely_ via our [Provider Plugin](https://github.com/saucelabs/testcafe-provider).

Unlike [saucectl](/dev/cli/saucectl/), which transmits and runs your TestCafe
tests directly on a Sauce Labs VM, the Sauce Labs [Provider Plugin](https://github.com/saucelabs/testcafe-provider)
allows TestCafe to connect to a browser session remotely, allowing for a greater
project setup flexibility.
While [saucectl](/dev/cli/saucectl/) directly runs your TestCafe tests on a
Sauce Labs VM, the Sauce Labs Provider Plugin enables remote browser sessions.
This offers greater project flexibility, as tests run in your environment.
You maintain full control over the Node.js versions, dependency management, and
build systems.

Additionally, you may run into limitations with saucectl when accessing internal
resources that aren't accessible via HTTP(S) or use [unsupported ports](/secure-connections/sauce-connect/advanced/specifications/#supported-browsers-and-ports).

We recommend that you give both approaches a try and pick the one that suits
your use case best.
Expand Down