Meteor-Community-Packages / Meteor-Community-Packages/meteor-browser-tests

TypeError: chrome.Options.chrome is not a function

Open
#54 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
13
Forks
23
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Client tests fail with type error.
both for 1.5.1 and 1.5.3

Unfortunately I can't tell what change caused it (linting error prevented running tests for almost a month)

Repo: https://gitlab.com/Openki/Openki

**Log**

```
I20231118-19:24:55.864(0)? 50 passing (129ms)
I20231118-19:24:55.864(0)?
I20231118-19:24:55.865(0)?
I20231118-19:24:55.865(0)? --------------------------------
I20231118-19:24:55.865(0)? ----- RUNNING CLIENT TESTS -----
I20231118-19:24:55.866(0)? --------------------------------
W20231118-19:24:55.883(0)? (STDERR) /root/.meteor/packages/meteortesting_mocha-core/.8.1.2.1pesrr7.nent++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mocha/lib/runner.js:906
W20231118-19:24:55.884(0)? (STDERR) throw err;
W20231118-19:24:55.885(0)? (STDERR) ^
W20231118-19:24:55.885(0)? (STDERR)
W20231118-19:24:55.885(0)? (STDERR) TypeError: chrome.Options.chrome is not a function
W20231118-19:24:55.886(0)? (STDERR) at startChrome (packages/meteortesting:browser-tests/browser/chromedriver.js:56:89)
W20231118-19:24:55.886(0)? (STDERR) at startBrowser (packages/meteortesting:browser-tests/server.js:28:7)
W20231118-19:24:55.895(0)? (STDERR) at clientTests (packages/meteortesting:mocha/server.js:148:3)
W20231118-19:24:55.895(0)? (STDERR) at packages/meteortesting:mocha/server.js:194:7
W20231118-19:24:55.895(0)? (STDERR) at packages/meteortesting:mocha/server.js:122:13
```

**Versions**
meteortesting:browser-tests@1.5.1
meteortesting:mocha@2.1.0
meteortesting:mocha-core@8.1.2

see https://gitlab.com/Openki/Openki/-/tree/dev/.meteor?ref_type=heads for all versions.

Any help welcome

Contributor guide

Open the contributing guide

Research direction

Start at packages/meteortesting:browser-tests/browser/chromedriver.js line 56, where startChrome fails, then follow its call from packages/meteortesting:browser-tests/server.js. Reproduce the client test run with the reported meteortesting package versions and inspect the Chrome driver API in use. Done means client tests start without the TypeError and complete successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.