-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Unit Tests throw error: "Uncaught Error: Assertion Failed: BUG: Render node exists without concomitant env" #178
Comments
I've been having a similar issue, but haven't had any luck in resolving it yet. |
+1 |
Here's a stack trace I have for this exact error:
|
Using Ember 1.13.5 and Ember-QUnit 0.4.2 this is now working for me |
Had the exact same error and using Ember 1.13.5 and ember-qunit 0.4.2 also solves it for me |
Closing issue because it has been fixed in qunit 0.4.2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently upgraded from ember 1.13.1 to ember 1.13.4 and am now getting this error on my unit tests: "Uncaught Error: Assertion Failed: BUG: Render node exists without concomitant env".
The only place I have seen any error messaging like this is here: https://github.com/emberjs/ember.js/blob/master/packages/ember-views/tests/views/view/class_name_bindings_test.js where in the final test the view's renderNode is set to null to prevent this issue.
The error is thrown for me on a component test. I have tried setting the render node to null on the component, along with messing around with the app on set up and tear down. Moving back to Ember 1.13.3 fixes the issue but I would like to be up to date if possible. Anyone know what is going on here?
The text was updated successfully, but these errors were encountered: