-
Notifications
You must be signed in to change notification settings - Fork 193
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
Switching over to using @testset
s
#251
Comments
Yes, this would be good. It's been on my to-do list for a while but I haven't gotten around to it. A PR would be welcome if you're interested in taking it on. |
Sure. I'm going to need to change a bunch of tests for #250, so maybe I'll just roll it in with that. |
That'd be fine, though having it as a separate PR (or at least a separate commit) would make it easier to review. |
Yeah, I was thinking I'd just adding an extra commit once that PR is ready. |
Just a heads-up - if you wrap all your tests in nested testsets, you won't see progress in Travis - the output is delayed until all tests are complete. (This can be a disadvantage.) |
The
@testset
macro (introduced in 0.5) provides nicer test reporting.The text was updated successfully, but these errors were encountered: