Meteor-Community-Packages / Meteor-Community-Packages/meteor-browser-tests
No sourcemaps for Selenium/headless chrome client tests?
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I could really use some assistance to get sourcemaps working for client-side callstacks in headless chrome.
My command looks something like this:
`>` `TEST_BROWSER_DRIVER=chrome TEST_CHROME_ARGS='start-maximized enable-automation --headless --no-sandbox --disable-dev-shm-usage --disable-browser-side-navigation --disable-gpu --ignore-certificate-errors' TEST_CLIENT=1 TEST_SERVER=1 ROOT_URL=https://www.dev-test.com:3000 SERVER_NODE_OPTIONS='--trace-uncaught --trace-warnings' meteor test --port 3006 --extra-packages xolvio:cleaner meteortesting:mocha@3.2.0 meteortesting:browser-tests@1.7.0 meteortesting:mocha-core@8.2.0 --driver-package meteortesting:mocha --full-app --settings test.json`
(3000 is the SSL port and 3006 is for HTTP; requests are proxied and work fine)
Anything obviously missing here? Am I barking up the right tree?
Thanks.
Contributor guide
Research direction
Start by reproducing the supplied `meteor test` command with the listed Chrome and browser-test settings. Inspect how client-side failures and callstacks are handled in the browser test package; done means headless Chrome reports usable source locations for client test failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100