-
Notifications
You must be signed in to change notification settings - Fork 783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.17.0 breaks phantomjs #733
Comments
Just Ignore this comment, My guess is wrong I guess this break does not cause by version 1.17, you may have old test runner html file(like the one used in 1.11.0)
to just
|
I mentioned this in #732 but I am getting the same error. |
Working on it, thanks for reporting. Setting I'm closing this one as this is a duplicate of #732 |
This does not happen only on phantomjs. I am running qunit tests using karma and after qunit updated to 1.17.0 getting following errors. Chrome |
I'm a bit puzzled. Should i apply the fix described by @mkoxio |
Better wait for the fix, but you can use the new qunit markup at anytime. from <h1 id="qunit-header">Tests</h1>
<h2 id="qunit-banner"></h2>
<div id="qunit-testrunner-toolbar"></div>
<h2 id="qunit-userAgent"></h2>
<ol id="qunit-tests"></ol> to <div id="qunit"></div> |
After applying the test filter in the HTML Reporter, a error were introduced when the toolbar element wasn't present at the DOM. Two tests html files are now created to allow testing the legacy QUnit markup and also to prevent tests from failing if the markup is not present. Fix qunitjs#732 Closes qunitjs#731 Ref qunitjs#733
Hi,
just updated
qunit
and my phantomjs gets stuck in:The text was updated successfully, but these errors were encountered: