Set Ember.testing only while actually running a test. #227
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.
Previously,
Ember.testing
was set totrue
in module scope ofember-test-helpers
module. This causes issues due to how Ember handles RSVP promises that happen whileEmber.testing
is truthy.This commit updates the various machinery to set
Ember.testing = true
when tests are starting, and reset it tofalse
once they've finished their teardown. It also adds assertions to ensure that each test properly cleans up after itself.Note: In some cases, instead of adding new assertions I used
throw new Error()
. This was only done in the "legacy" tests as a way of ensuring the required functionality without modifying allassert.expect()
counts throughout those test files.Partially addresses emberjs/ember-qunit#246.