-
Notifications
You must be signed in to change notification settings - Fork 779
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
Global beforeEach
/afterEach
should synchronize before module beforeEach
/afterEach
run
#647
Labels
Type: Bug
Something isn't working right.
Comments
Also, just to add the idea into the mix now: related to #543, Mocha's strategy for infinitely nested modules (suites) is basically accomplished by 2 decisions:
If we are going to pursue #543 (and I really hope we do), this is very important to keep in mind. |
leobalter
added a commit
to leobalter/qunit
that referenced
this issue
Sep 3, 2014
leobalter
added a commit
to leobalter/qunit
that referenced
this issue
Sep 3, 2014
leobalter
added a commit
to leobalter/qunit
that referenced
this issue
Sep 3, 2014
leobalter
added a commit
to leobalter/qunit
that referenced
this issue
Sep 3, 2014
leobalter
added a commit
to leobalter/qunit
that referenced
this issue
Sep 4, 2014
jzaefferer
added a commit
to jzaefferer/qunit
that referenced
this issue
Oct 10, 2014
Between locating the hooks in `QUnit` or `QUnit.config` and making them simple setters and callback lists (like QUnit.done et al) and upcoming plans for nested suites, we decided not to release this feature, for now. I'm keeping the abstractions for hooks in place, so it should be trivial to bring this back in whatever form we decide on later. Effectively reverts 5ee31a0 and follow-up commits. Fixes qunitjs#665 Ref qunitjs#633 Ref qunitjs#635 Ref qunitjs#647
jzaefferer
added a commit
to jzaefferer/qunit
that referenced
this issue
Oct 17, 2014
Between locating the hooks in `QUnit` or `QUnit.config` and making them simple setters and callback lists (like QUnit.done et al) and upcoming plans for nested suites, we decided not to release this feature, for now. I'm keeping the abstractions for hooks in place, so it should be trivial to bring this back in whatever form we decide on later. Effectively reverts 5ee31a0 and follow-up commits. Fixes qunitjs#665 Ref qunitjs#633 Ref qunitjs#635 Ref qunitjs#647
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As noted in #634 (comment) and #634 (comment), there is a bug in the newly introduced
beforeEach
/afterEach
hooks: the globalbeforeEach
/afterEach
hooks should be allowed fully synchronize before the module-levelbeforeEach
/afterEach
hooks are run. If they don't, it easily leads to race conditions.The text was updated successfully, but these errors were encountered: