This repository has been archived by the owner on Dec 10, 2024. It is now read-only.
Add destroy step to instance-initializer test blueprint #110
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| appInstance = application.buildInstance(); | ||
| }); | ||
| }); | ||
|
|
||
| afterEach(function() { | ||
| application.destroy(); |
There was a problem hiding this comment.
We should import and use the run-destroy test helper...
|
pinging @rwjblue |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Had multiple instance-initializer tests generated and came across this:
Assertion Failed: You cannot use the same root element (body) multiple times in an Ember.ApplicationPresumably it was because applications were getting created but not destroyed, so implemented a destroy step in the blueprint. That fixed it but if there's a better way please let me know