Tests not running on Saucelabs #1497
Comments
|
I was wrong about that: The real cause for the failing test was the following. One of the new testcases I wrote for the security issue, was using the ES6 The specs are not compiled by babel, so this testcase caused an error in IE10 and IE11, which it probably whould have shown in the dev-tools, if that had been visible. This ultimately was the reason that the tests did not even start. |
nknapp
added a commit
that referenced
this issue
Mar 15, 2019
Internet Explorer does not support the 'class Testclass {}' notation,
and tests are not compiled using babel.
closes #1497
nknapp
added a commit
that referenced
this issue
Mar 15, 2019
Internet Explorer does not support the 'class Testclass {}' notation,
and tests are not compiled using babel.
closes #1497
|
Released in 4.0.14 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have multiple travis-ci builds failing now, where it seems that the problem is the SauceLabs infrastructure rather than the tests themselves.
We could either talk to Saucelabs about that. See the failed builds for issue 1495 for details.
Or we could switch to a Browerstack open-source plan,
The text was updated successfully, but these errors were encountered: