[FSSDK-13413] Remove the old browser/UMD test setup and Karma leftovers

.eslintignore

@@ -1,3 +1,2 @@
 *.tests.js
-*.umdtests.js
 test_data.js

.github/workflows/javascript.yml

@@ -107,8 +107,7 @@ jobs:
       TEST_BROWSER: ${{ matrix.browser }}
     steps:
     - uses: actions/checkout@v3
-    # Runs the browser tests with Vitest 5 from tests/browser (see its README).
-    # Needs Node 22.23.4+ (Vitest 5 / webdriverio); the root project stays on Vitest 3 for Node 18.
+    # Browser and UMD tests run from tests/browser (see its README), which needs Node 22.23.4+.
     - name: Set up Node
       uses: actions/setup-node@v3
       with:
@@ -135,25 +134,6 @@ jobs:
       working-directory: ./tests/browser
       run: npm run test-umd
 
-  # crossbrowser_and_umd_unit_tests:
-  #   runs-on: ubuntu-latest
-  #   env:
-  #     BROWSER_STACK_USERNAME: ${{ secrets.BROWSERSTACK_USERNAME }}
-  #     BROWSER_STACK_ACCESS_KEY: ${{ secrets.BROWSERSTACK_ACCESS_KEY }}
-  #   steps:
-  #   - uses: actions/checkout@v3
-  #   - name: Set up Node
-  #     uses: actions/setup-node@v3
-  #     with:
-  #       node-version: 16
-  #       cache: 'npm'
-  #       cache-dependency-path: ./package-lock.json
-  #   - name: Cross-browser and umd unit tests
-  #     working-directory: .
-  #     run: |
-  #       npm install
-  #       npm run test-ci
-
   generate_messages_test:
     runs-on: ubuntu-latest
     steps:

.platform-isolation.config.js

@@ -23,7 +23,6 @@ module.exports = {
     '**/*.test.js',
     '**/*.spec.js',
     '**/*.tests.js',
-    '**/*.umdtests.js',
     '**/*.test-d.ts',
 
     // Generated files

README.md

@@ -231,7 +231,7 @@ To run unit tests, you can take the following steps:
 2. Run `npm test` to run all test files.
 3. Run `npm run test-vitest` to run only tests written using Vitest.
 4. Run `npm run test-mocha` to run only tests written using Mocha.
-5. (For cross-browser testing) Run `npm run test-browser-browserstack` to run browser tests via BrowserStack, or `npm run test-browser-local` to run them locally.
+5. (For cross-browser testing) Browser and UMD tests live in a separate project, [tests/browser](tests/browser) (Node 22.23.4+). Run `npm install` there, then `npm run test-browser-browserstack` to run browser tests via BrowserStack, or `npm run test-browser-local` to run them locally. See [tests/browser/README.md](tests/browser/README.md).
 6. Resolve any tests that fail before continuing with your contribution.
 
 This information is relevant only if you plan on contributing to the SDK itself.
@@ -243,6 +243,10 @@ npm install
 # Run unit tests.
 npm test
 
+# Browser and UMD tests run from tests/browser (needs Node 22.23.4+).
+cd tests/browser
+npm install
+
 # Run browser tests locally.
 npm run test-browser-local
 
@@ -256,7 +260,7 @@ npm run test-browser-browserstack
 npm run test-umd-browserstack
 ```
 
-[/.github/workflows/javascript.yml](/.github/workflows/javascript.yml) contains the definitions for `BROWSERSTACK_USERNAME` and `BROWSERSTACK_ACCESS_KEY` used in the GitHub Actions CI pipeline. When developing locally, you must provide your own credentials in order to run `npm run test-browser-browserstack`. You can register for an account for free on [the BrowserStack official website here](https://www.browserstack.com/).
+[/.github/workflows/javascript.yml](/.github/workflows/javascript.yml) contains the definitions for `BROWSERSTACK_USERNAME` and `BROWSERSTACK_ACCESS_KEY` used in the GitHub Actions CI pipeline. When developing locally, you must provide your own credentials in order to run `npm run test-browser-browserstack` in `tests/browser`. You can register for an account for free on [the BrowserStack official website here](https://www.browserstack.com/).
 
 ### Contributing