Skip to content
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

Expose current test information to beforeEach/afterEach, fixes #794, #797 #795

Merged
merged 2 commits into from
Jul 1, 2013
Merged

Conversation

avaly
Copy link
Contributor

@avaly avaly commented Apr 5, 2013

Feature description: #794 , #797

@jlipps
Copy link

jlipps commented Apr 8, 2013

👍

@bootstraponline
Copy link

👍

1 similar comment
@maudineormsby
Copy link

👍

@jlipps
Copy link

jlipps commented Jun 13, 2013

Any reason this simple and useful 2-line change has gone unreviewed and unmerged for 2 months?

@ananthakumaran
Copy link

👍

1 similar comment
@alexgorbatchev
Copy link

👍

@tj
Copy link
Contributor

tj commented Jul 1, 2013

I've had this discussion somewhere in the issue queue before, I still question what the use-case would be

tj added a commit that referenced this pull request Jul 1, 2013
Expose current test information to beforeEach/afterEach, fixes #794, #797
@tj tj merged commit 8bc84fc into mochajs:master Jul 1, 2013
@ivolucien
Copy link

For posterity, this is a great help in identifying which test fails when a test's output does not uniquely identify the test in question. Having the file and title exposed is exactly what we needed to immediately find the problem test. By far easier than process of elimination.

@xbill82
Copy link

xbill82 commented Sep 10, 2018

Hi, was this feature documented? Can't find it in docs...

@relsqui
Copy link

relsqui commented Oct 10, 2018

For the next person who comes here wishing this feature was documented: the state values appear to be the strings failed and passed, per https://github.com/mochajs/mocha/blob/master/lib/runner.js

@boneskull boneskull added this to the v6.0.0 milestone Nov 5, 2018
@lotosotol
Copy link

lotosotol commented Mar 20, 2019

hmmm... and how do I retrieve the status of the test suite before (or after) closing the browser or calling the .quit() method?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.