Skip to content
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

QUnit tests fail with "Script error ..." #44

Open
jayarjo opened this issue May 10, 2013 · 0 comments · May be fixed by #45
Open

QUnit tests fail with "Script error ..." #44

jayarjo opened this issue May 10, 2013 · 0 comments · May be fixed by #45

Comments

@jayarjo
Copy link

jayarjo commented May 10, 2013

All QUnit tests fail in all browsers with:

Uncaught Error: pushFailure() assertion outside test context, was     at F.QUnit.start (.../qunit.js:464:10)`, unless I set `QUnit.config.autostart = false;

The problem is at: lib/hub/view/public/inject.js#L7:

// Do not start QUnit tests before bind,
// we need to setup logging callbacks first.
if (window.QUnit && window.QUnit.config) {
    window.QUnit.config.autostart = false;
}

This is executed when there is no QUnit in global space yet (inject.js is always the first script, in fact yeti makes sure it to be first) - code above has no chance to execute, ever.

So autostart is never disabled and QUnit.start() is run twice.

@ghost ghost assigned clarle May 13, 2013
okuryu pushed a commit to okuryu/yeti that referenced this issue Jul 27, 2013
This allows Yeti to be used in environments where an
internet connection is not available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants