Pin tests to chrome 129

Workaround an issue with testcafe + chrome 130+
saucelabs · Oct 18, 2024 · 6161bc3 · 6161bc3
1 parent ac83c24
commit 6161bc3
Show file tree

Hide file tree

Showing 5 changed files with 51 additions and 0 deletions.
diff --git a/tests/cloud/.sauce/config-proxy.yml b/tests/cloud/.sauce/config-proxy.yml
@@ -18,13 +18,19 @@ suites:
   - name: "Proxy - macOS13"
     platformName: "macOS 13"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     timeout: 2m
     src:
       - "tests/sc/*.test.js"
     speed: 1
   - name: "Proxy - Win11"
     platformName: "Windows 11"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     timeout: 2m
     src:
       - "tests/sc/*.test.js"

diff --git a/tests/cloud/.sauce/config-sc.yml b/tests/cloud/.sauce/config-sc.yml
@@ -18,6 +18,9 @@ suites:
   - name: "Win10 - Chrome"
     platformName: "Windows 10"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/**/*.test.js"
     speed: 1
@@ -31,6 +34,9 @@ suites:
   - name: "Win11 - Chrome"
     platformName: "Windows 11"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/**/*.test.js"
     speed: 1
@@ -44,6 +50,9 @@ suites:
   - name: "macOS11 - Chrome"
     platformName: "macOS 11.00"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/**/*.test.js"
     speed: 1
@@ -63,6 +72,9 @@ suites:
   - name: "macOS12 - Chrome"
     platformName: "macOS 12"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/**/*.test.js"
     speed: 1
@@ -82,6 +94,9 @@ suites:
   - name: "macOS13 - Chrome"
     platformName: "macOS 13"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/**/*.test.js"
     speed: 1

diff --git a/tests/cloud/.sauce/config.yml b/tests/cloud/.sauce/config.yml
@@ -18,6 +18,9 @@ suites:
   - name: "Win10 - Chrome"
     platformName: "Windows 10"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/no-sc/**/*.test.js"
     speed: 1
@@ -31,6 +34,9 @@ suites:
   - name: "Win11 - Chrome"
     platformName: "Windows 11"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/no-sc/**/*.test.js"
     speed: 1
@@ -44,6 +50,9 @@ suites:
   - name: "macOS11 - Chrome"
     platformName: "macOS 11.00"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/no-sc/**/*.test.js"
     speed: 1
@@ -63,6 +72,9 @@ suites:
   - name: "macOS12 - Chrome"
     platformName: "macOS 12"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/no-sc/**/*.test.js"
     speed: 1
@@ -82,6 +94,9 @@ suites:
   - name: "macOS13 - Chrome"
     platformName: "macOS 13"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     src:
       - "tests/no-sc/**/*.test.js"
     speed: 1

diff --git a/tests/post-release/.sauce/config_mac.yml b/tests/post-release/.sauce/config_mac.yml
@@ -26,6 +26,9 @@ suites:
 
   - name: "test chrome on mac 11"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     platformName: "macOS 11.00"
     src:
       - "**/*.test.js"
@@ -50,6 +53,9 @@ suites:
 
   - name: "test chrome on mac 12"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     platformName: "macOS 12"
     src:
       - "**/*.test.js"
@@ -74,6 +80,9 @@ suites:
 
   - name: "test chrome on mac 13"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     platformName: "macOS 13"
     src:
       - "**/*.test.js"

diff --git a/tests/post-release/.sauce/config_win.yml b/tests/post-release/.sauce/config_win.yml
@@ -20,6 +20,9 @@ suites:
 #########################
   - name: "test chrome on windows 10"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     platformName: "Windows 10"
     src:
       - "**/*.test.js"
@@ -38,6 +41,9 @@ suites:
 
   - name: "test chrome on windows 11"
     browserName: "chrome"
+    # FIX: Pinning to 129 to workaround current issue using testcafe with
+    # chrome 130+.
+    browserVersion: "129"
     platformName: "Windows 11"
     src:
       - "**/*.test.js"