From 7ec8ef7cb339def96e8333eb75d883d1665b4045 Mon Sep 17 00:00:00 2001
From: Paul Gschwendtner <paulgschwendtner@gmail.com>
Date: Mon, 21 Sep 2020 21:14:59 +0200
Subject: [PATCH] build: setup default browser for running legacy tests locally

Sometimes the legacy Karma tests might fail and one might want
to debug those. Currently the Gulp task can be run for that, but
it's not starting any browser so one needs to launch Chrome manually.

Tests usually fail then because the browser has different dimensions
but our test expectations rely on a specific dimension. i.e. 1024x768
---
 test/karma-browsers.json | 6 ++++++
 test/karma.conf.js       | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/test/karma-browsers.json b/test/karma-browsers.json
index ea682ee6d5b3..9aac4380c064 100644
--- a/test/karma-browsers.json
+++ b/test/karma-browsers.json
@@ -6,6 +6,12 @@
       "--no-sandbox"
     ]
   },
+  "ChromeLocalDebug": {
+    "base": "Chrome",
+    "flags": [
+      "--window-size=1024,768"
+    ]
+  },
   "SAUCELABS_IOS13": {
     "base": "SauceLabs",
     "browserName": "Safari",
diff --git a/test/karma.conf.js b/test/karma.conf.js
index ae05dee92c60..0c0840a91c18 100644
--- a/test/karma.conf.js
+++ b/test/karma.conf.js
@@ -106,7 +106,7 @@ module.exports = config => {
     browserDisconnectTolerance: 1,
     browserNoActivityTimeout: 300000,
 
-    browsers: [],
+    browsers: ['ChromeLocalDebug'],
     singleRun: false,
 
     // Try Websocket for a faster transmission first. Fallback to polling if necessary.