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

Refactoring base's runtests harness for packages to use too #18740

Closed
tkelman opened this issue Sep 30, 2016 · 1 comment
Closed

Refactoring base's runtests harness for packages to use too #18740

tkelman opened this issue Sep 30, 2016 · 1 comment
Assignees
Labels
packages Package management and loading testsystem The unit testing framework and Test stdlib

Comments

@tkelman
Copy link
Contributor

tkelman commented Sep 30, 2016

Ref #17165 (comment), we should try to refactor what's currently in test/runtests.jl to instead be a default part of the Base.Test module so packages can also use it for pretty-printing, parallel execution, running of selective subsets of tests (related to #15404), and everything else that base's tests do but packages have to roll their own.

@tkelman tkelman added packages Package management and loading testsystem The unit testing framework and Test stdlib labels Sep 30, 2016
@kshyatt kshyatt self-assigned this Sep 30, 2016
@kshyatt
Copy link
Contributor

kshyatt commented Dec 8, 2016

OK, so you ought to be able to give runtests function two args: a test dir (which may be base Julia test/ or joinpath(Pkg.dir(), test)) and a list of test files to run - and if we have that, I think it should work? We might want to include sharding (like we have now for base, where all linalg tests run first)? Anything else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
packages Package management and loading testsystem The unit testing framework and Test stdlib
Projects
None yet
Development

No branches or pull requests

3 participants