Skip to content

Commit

Permalink
Merge branch 'main' into lee-snyder133-patch-2
Browse files Browse the repository at this point in the history
  • Loading branch information
si-net authored Jan 10, 2025
2 parents 2b196cc + 7101a3f commit 2f0316e
Show file tree
Hide file tree
Showing 4 changed files with 14 additions and 11 deletions.
4 changes: 2 additions & 2 deletions docs/secure-connections/sauce-connect.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ title: Sauce Connect Proxy 4
sidebar_label: Overview
---

:::caution Sauce Connect Proxy 5 is released
Please refer to [Sauce Connect Proxy 5 Overview](/secure-connections/sauce-connect-5/) for the most recent Sauce Connect Proxy documentation.
:::caution Important Notice: Sauce Connect 4 is reaching end-of-life status.
Starting May 5, 2025, servers will no longer support Sauce Connect version 4 traffic. To avoid interruptions, upgrade to [Sauce Connect 5](/secure-connections/sauce-connect-5/migrating) at your earliest convenience.
:::

If your company has firewall rules that limit your ability to run tests on Sauce Labs, you can use our Sauce Connect Proxy feature to connect to Sauce Labs in the cloud without exposing your company's IT infrastructure to security risks.
Expand Down
5 changes: 2 additions & 3 deletions docs/secure-connections/sauce-connect/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,5 @@ title: Downloading Sauce Connect Proxy
sidebar_label: Download
---

Sauce Connect 4 has entered end-of-life status. The servers will be turned off on May 5, 2025.

We recommend upgrading to [Sauce Connect 5](/secure-connections/sauce-connect-5/installation).
Sauce Connect 4 is reaching end-of-life status.
Starting May 5, 2025, servers will no longer support Sauce Connect version 4 traffic. To avoid interruptions, upgrade to [Sauce Connect 5](/secure-connections/sauce-connect-5/migrating) at your earliest convenience.
4 changes: 2 additions & 2 deletions docs/secure-connections/sauce-connect/quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

:::caution Sauce Connect Proxy 5 is released
Please refer to [Sauce Connect Proxy 5 Quickstart Guide](/secure-connections/sauce-connect-5/quickstart/) for the latest quickstart guide.
:::caution Important Notice: Sauce Connect 4 is reaching end-of-life status.
Starting May 5, 2025, servers will no longer support Sauce Connect version 4 traffic. To avoid interruptions, upgrade to [Sauce Connect 5](/secure-connections/sauce-connect-5/migrating) at your earliest convenience.
:::

Sauce Connect is required to run a local test on an app or website located behind a firewall. Get up and running with a basic Sauce Connect Proxy tunnel in minutes using the steps below.
Expand Down
12 changes: 8 additions & 4 deletions docs/web-apps/automated-testing/electron.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,19 +21,23 @@ Sauce Labs currently supports the following test configurations for Electron.
- MacOS 13
- (Linux support to be decided)
- Electron versions
- versions 5 - 31 inclusive
- versions 5 - 32 inclusive

## How to Get Started

### App management

Upload a zip file containing your Electron app via [REST API](/mobile-apps/app-storage/#upload-apps-via-rest-api). You can refer to uploaded apps by either the file ID or filename. Note that as with mobile apps, Electron apps are accessible only to members of the same team, and retained for 60 days.
Upload a zip or dmg archive file containing your Electron app via [REST API](/mobile-apps/app-storage/#upload-apps-via-rest-api). You can refer to uploaded apps by either the file ID or filename. Note that as with mobile apps, Electron apps are accessible only to members of the same team, and retained for 60 days.

### Binary location

The `binary_location` is the folderpath and filename of your Electron executable within your zip file structure.
The `binary_location` is the folderpath and filename of your Electron executable in your archive file structure.

For example, if your zip file is structured like this:
You don't normally need to provide this field. If you omit it, our systems will do their best to find the executable in the file you uploaded.

If that fails, provide the binary path as described below.

If your archive file is structured like this:
```
SauceLabsElectronAppv1.zip
-- [ Sauce Labs Test ]
Expand Down

0 comments on commit 2f0316e

Please sign in to comment.