-
Notifications
You must be signed in to change notification settings - Fork 14
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
@testset Scope #174
Labels
enhancement
New feature or request
Comments
On the topic of test management, we should consider executing testsets in parallel. In the best case this can reduce the time spent testing from sum(time.(tests)) to maxmimum(time.(tests)). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During last week's hackathon, a non-negligible amount of developer time was spent tracking down the following error:
@test
was written which assigned a local variable the named
using CombinatorialSpaces
d
@testsets
meant that a helpful error message was thrown at the line where the local variabled
was declaredErrors in our test suite should not depend on the order in which testsets are included. Each testset should be contained.
So, we should look into how to prevent this behavior. I immediately want to use
let ... end
blocks, but it appears that there is some advice on testset scoping that I haven't fully grasped: https://discourse.julialang.org/t/testset-scoping/17025Perhaps we have poor
module
management in the test suite.The text was updated successfully, but these errors were encountered: