You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ember-qunit sets Ember.testing to true on loading.
This is causing issues in my set-up, where i load ember-qunit and application. If ember-qunit is executed before the application, application initialization throws following assertion.
"You have turned on testing mode, which disabled the run-loop's autorun. You will need to wrap any code with asynchronous side-effects in an Ember.run"
commenting out Ember.testing=true, solved the issue. I think it is better to allow user to set this by calling setupForTesting() on Application
The text was updated successfully, but these errors were encountered:
I am using Karma-runner to run test cases. Using karma-requirejs to load application code, libraries and ember-qunit. To solve this issue i mentioned application as dependency to ember-qunit.
Are you planning to fix this or this issue cannot be fixed?
You should follow the warning and wrap that code in Ember.run, I think this would be the case with ember's default testing helpers anyway. If you feel strongly that we should reopen this issue, please do, but your async stuff should be wrapped in an Ember.run anyway.
Currently, ember-qunit sets Ember.testing to true on loading.
This is causing issues in my set-up, where i load ember-qunit and application. If ember-qunit is executed before the application, application initialization throws following assertion.
"You have turned on testing mode, which disabled the run-loop's autorun. You will need to wrap any code with asynchronous side-effects in an Ember.run"
commenting out Ember.testing=true, solved the issue. I think it is better to allow user to set this by calling setupForTesting() on Application
The text was updated successfully, but these errors were encountered: