-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Work towards using QUnit 2 APIs. #16061
Conversation
Supports both `teardown` and `afterEach` for now...
@thoov - This is somewhat related to the general purpose "test cleanup" quest issue, would you mind reviewing? |
@@ -108,5 +108,5 @@ function assertDirty(obj, callback, label) { | |||
let tag = tagFor(obj); | |||
let tagValue = tag.value(); | |||
callback(); | |||
ok(!tag.validate(tagValue), label); | |||
QUnit.config.current.assert.ok(!tag.validate(tagValue), label); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whats your take on this vs passing assert into assertDirty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just my own laziness I think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is just one occurrence of assertDirty so I say we hook it up and then merge this
Other than the one comment I had it LGTM. Tagging #15988 so it shows up on the quest issue |
This is 🍌s and I don't like it one bit, but I also don't want to wait 3 times as long for the test suite to finish.
Migrates ember-runtime and ember-metal to using QUnit 2 APIs (avoiding global assertions, using beforeEach/afterEach instead of setup/teardown, etc).
It also updates the test harness for
moduleFor
and the olderember-dev
system to honor bothsetup
/teardown
andbeforeEach
/afterEach
.