From 6bd218f6de0e67074abbf6fef859f905c8a7841f Mon Sep 17 00:00:00 2001 From: Alex Plischke Date: Thu, 19 Sep 2024 09:30:47 -0700 Subject: [PATCH] docs: testcafe browser provider benefits (#2950) --- .../automated-testing/testcafe/provider-plugin.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/web-apps/automated-testing/testcafe/provider-plugin.md b/docs/web-apps/automated-testing/testcafe/provider-plugin.md index 7626912670..0eeae907b8 100644 --- a/docs/web-apps/automated-testing/testcafe/provider-plugin.md +++ b/docs/web-apps/automated-testing/testcafe/provider-plugin.md @@ -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.