Skip to content

test-runner-browserstack 0.5.0 fails when a non-chrome browser is specified  #1894

Open
@emensch

Description

@emensch

Regression when upgrading from 0.4.4 to 0.5.0.

Minimal reproduction with this configuration:

import { esbuildPlugin } from "@web/dev-server-esbuild";
import { browserstackLauncher } from "@web/test-runner-browserstack";

export default {
  nodeResolve: true,
  files: '*.spec.ts',
  plugins: [
    esbuildPlugin({ ts: true }),
  ],
  browsers: [
    browserstackLauncher({
      capabilities: {
        'browserstack.user': '[redacted]',
        'browserstack.key': '[redacted]',
        project: 'Test project',
        build: 'local',
        os: 'OS X',
        os_version: 'Big Sur',
        name: 'Test',
        browserName: 'firefox',
        browser_version: 'latest',
      }
    })
  ],
}

logs the following error:

Invalid or unsupported WebDriver capabilities found ("browserstack.user", "browserstack.key", "project", "build", "os", "os_version", "name", "browser_version", "timeout", "browserstack.local", "browserstack.localIdentifier", "browserstack.ie.enablePopups", "browserstack.edge.enablePopups", "browserstack.safari.enablePopups"). Ensure to only use valid W3C WebDriver capabilities (see https://w3c.github.io/webdriver/#capabilities).If you run your tests on a remote vendor, like Sauce Labs or BrowserStack, make sure that you put them into vendor specific capabilities, e.g. "sauce:options" or "bstack:options". Please reach out to to your vendor support team if you have further questions.

I've observed this behavior with browserName set to firefox and safari. No issues when set to chrome.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions