-
-
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
Integration test method to "destroy" the component #217
Comments
I was able to emulate the behavior by passing an attribute named isDestroyed to the component and setting it to true... :) |
In more recent ember-qunit versions, you can do:
|
@rwjblue thanks |
@rwjblue how do I implement this?
|
@jakeleboeuf you probably found the solution, but try importing Import: Then call directly: |
Is there a way to destroy the tested component in integration tests?
I had the issue where async behavior were setting internal properties on the component on completion. The problem is sometimes the component was destroyed before the async behavior had completed, resulting in an error.
While I fixed the code to handle this situation I would have liked to implement a corresponding test. And maybe use something such as
this.destroy()
to check the race condition.The text was updated successfully, but these errors were encountered: