Open hekod777 opened 6 years ago
Could you try and look at the automatically opened Chrome browser, in the console, and see which error you are getting?
I have a similar issue, my test suite fails on a timeout too, trying to run a test with a11ySuite
.
In my console I see the error:
at Suite.a11ySuite.eachTest (a11ySuite.js:51)
at mocha.js:1550
at Object.exports.forEach (mocha.js:1595)
at Suite.eachTest (mocha.js:1550)
at Runner.grepTotal (mocha.js:1224)
at Runner.grep (mocha.js:1215)
at new Runner (mocha.js:1197)
at Mocha.run (mocha.js:592)
at _runMocha (extend.js:41)
at done (util.js:34)```
More details here: https://stackoverflow.com/questions/50517884/polymer-3-0-a11ysuite-testing-error
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
In case this helps anyone, we had a similar timeout issue when upgrading to wct 6 and enabling the npm
option. Inspection of the network requests in the browser showed that it was hanging for a long time waiting for our JS bundles from the local Polyserve server. Turned out it was trying to auto-transpile our (already-preprocessed) files with Babel. Turning off the auto-transpilation worked to return us to a reasonable startup time, with the options {compile: 'never', moduleResolution: 'none'}
.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I am trying to move our polymer dependencies from
bower
tonpm
With the following imports in the
test.html
polymer test
worked successfully withbower_components
folder.but
polymer test --npm
orwct --npm
both gave me a Timed out error after about 1 minute.I have tried
wct
6.4.0, 6.5.0, 6.6.0-pre.5, all have this issue.here is the verbose log:
Any ideas how to get it to work?