Existing run loop at the beginning of test interferes with `Ember.run.join` behavior
Open
breaking
internal
- Dominant language
- JavaScript
- Stars
- 130
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure if this is intentional, but the behavior is definitely different from what `ember-qunit` have. Unit tests should not have a run loop started already.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.