-
Notifications
You must be signed in to change notification settings - Fork 18
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
Allow multiple mocha test suites #14
base: master
Are you sure you want to change the base?
Conversation
Hey are you using just saucie or ember-cli? |
I'm using testem. |
Would you mind squashing your commits and adding a test? |
…ust the first object, fixed leaking globals
Squashed the commits, are there already tests for mocha or just QUnit? |
atm only qunit, I can look into adding a test if you prefer, but I won't have time until the end of the week. |
You might want to check it out... This PR makes it work for my purposes but no matter how many tests you have it will always report just one test. |
Yep, I didn't found a way to access mocha test results reliable in every env. The best way (and what I currently do in ember-cli-sauce) is to add something like this to your tests:
saucie will detect this variable automatically and prefer it over manually parsing mocha results. |
That's what that's for!! It looks like the mocha results are a tree, you could probably iterate through it to get a running total. |
When tests on suites other than the first one were failing it would not report it. This appears to fix that issue.
It also checks the pending property of the tests so it doesn't report that it's done ahead of time.