-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Only skip current suite if error in beforeEach or beforeAll [Fix #581] #664
Conversation
…sts from the current suite, but carry on with other suites as normal.
This reverts commit 9d0d868.
this seems to mostly work, however if you have a beforeEach the nested suites will still execute beforeEach, even though a parent one has failed, ill see if i can get that working quickly here |
Oops - sorry, good catch. On Nov 28, 2012, at 4:08 PM, TJ Holowaychuk notifications@github.com wrote:
|
@dansitu Any update on this pull request? I'm having an issue writing my custom reporter because when there's an error inside hooks, the runner doesn't emit the |
I was in a hurry and didn't have time to make the fix @visionmedia suggested. @piuccio, maybe you'll have better luck? |
I'll see if I can work on it |
Any reason to not just blow away the children suites of the current suite when failHook is called?
This solves for the issue with beforeEach and nested suites. |
fixed by #1043 |
A failed beforeEach or beforeAll hook will now only cause the current suite to be skipped, rather than terminating the entire run.
Fix for #581