Closed motss closed 5 years ago
Seems to be running on Chrome 71.0.3578.98 on my MacBook Pro. Here's the output:
➜ pwa-starter-kit git:(master) ✗ npm run test
> pwa-starter-kit@0.9.0 test /Users/keanulee/Code/Polymer/pwa-starter-kit
> npm run test:unit && npm run test:integration
> pwa-starter-kit@0.9.0 test:unit /Users/keanulee/Code/Polymer/pwa-starter-kit
> polymer test --module-resolution=node --npm
Installing and starting Selenium server for local browsers
Selenium server running on port 61351
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB. chrome 71 ()
chrome 73 Beginning tests via http://localhost:8081/components/pwa-starter-kit/generated-index.html?cli_browser_id=0
chrome 71 Beginning tests via http://localhost:8081/components/pwa-starter-kit/generated-index.html?cli_browser_id=1
chrome failed to maximize
chrome failed to maximize
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB. chrome 71 ()
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
firefox 64 Beginning tests via http://localhost:8081/components/pwa-starter-kit/generated-index.html?cli_browser_id=2
safari 12.0.2 Beginning tests via http://localhost:8081/components/pwa-starter-kit/generated-index.html?cli_browser_id=3
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB. chrome 71 ()
[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
chrome 71 Tests passed
firefox 64 Tests passed
safari 12.0.2 Tests passed
chrome 73 Tests passed
Test run ended with great success
chrome 73 (16/0/0) chrome 71 (16/0/0)
firefox 64 (16/0/0) safari 12.0.2 (16/0/0)
> pwa-starter-kit@0.9.0 test:integration /Users/keanulee/Code/Polymer/pwa-starter-kit
> mocha test/integration --timeout=10000
routing tests
✓ the page selector switches pages (4679ms)
✓ the page selector switches pages in a different way (971ms)
👀 page screenshots are correct
wide screen
📸 wide/index.png => 66027 bytes, 0% different
✓ /index.html (1300ms)
📸 wide/view1.png => 66027 bytes, 0% different
✓ /view1 (1185ms)
📸 wide/view2.png => 63005 bytes, 0% different
✓ /view2 (1253ms)
📸 wide/view3.png => 63602 bytes, 0% different
✓ /view3 (1167ms)
📸 wide/batmanNotAView.png => 27828 bytes, 0% different
✓ /404 (1219ms)
narrow screen
📸 narrow/index.png => 76494 bytes, 0% different
✓ /index.html (928ms)
📸 narrow/view1.png => 76494 bytes, 0% different
✓ /view1 (1013ms)
📸 narrow/view2.png => 62540 bytes, 0% different
✓ /view2 (1105ms)
📸 narrow/view3.png => 64257 bytes, 0% different
✓ /view3 (958ms)
📸 narrow/batmanNotAView.png => 20855 bytes, 0% different
✓ /404 (979ms)
12 passing (23s)
➜ pwa-starter-kit git:(master) ✗
Just got new finding. It does not work on Java with version greater than 8. Downgrading to Java 8 just works. Found this issue thread https://github.com/Polymer/tools/issues/405 that might be helpful.
Thank you.
A simple command
npm run test
should run all tests and pass beautifully. But for some reasons, I'm having issues running tests without any issues on Chrome 71 and above on my MBP. Strange enough to see tests pass on TravisCI without timeout errors and stuff like that.Would like to know if this happens to me only? Is there anything can be done to improve this?