Skip to content

fix: Use https to access browserstack #176

fix: Use https to access browserstack

fix: Use https to access browserstack #176

Triggered via push August 20, 2024 09:34
Status Failure
Total duration 1m 13s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
test/browsers/browserstack.test.ts > BrowserStack browserCreator > should propagate configuration to browser stack: test/browsers/browserstack.test.ts#L49
AssertionError: expected { logLevel: 'error', …(9) } to deeply equal ObjectContaining{…} - Expected + Received - ObjectContaining { + Object { + "baseUrl": undefined, "capabilities": Object { "browserName": "chrome", - "bstack:options": ObjectContaining { + "bstack:options": Object { "accessKey": "my-key", + "buildName": undefined, + "os": "Windows", + "osVersion": "10", "projectName": "project", + "seleniumVersion": "3.5.2", "userName": "my-user", }, }, + "connectionRetryCount": 3, + "connectionRetryTimeout": 240000, "hostname": "hub.browserstack.com", + "logLevel": "error", "path": "/wd/hub", - "port": 80, - "protocol": "http", + "port": 443, + "protocol": "https", + "waitforTimeout": 5000, } ❯ test/browsers/browserstack.test.ts:49:29
release / release
Process completed with exit code 1.
release / release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/