testsets argument to Pkg.test()

[rofinn]

With the new testsets approach it would be nice if Pkg.test took an optional list of testset names to run.

Ex) Pkg.test(Foo, ["unit", "integration", "lint"]; coverage=true)

[tkelman]

Pkg.test right now makes no assumptions about the contents of runtests.jl. This might be better as a separate test-runner function that would take a file name? Maybe Pkg.test could take a list of ARGS though, then the contents of runtests.jl could handle them however you like.

[davidanthoff]

Just want to second this issue, any ability to specify the testset to run would be fantastic.

[kshyatt]

After #17165 is good to go we can add this in a new PR, I think. To that effect: if people can find more ways to break that PR/review it for bad things, it would be great!

[musm]

A lot of people have shown interest for such a feature, e.g.: https://discourse.julialang.org/t/test-specific-test-sets-in-julia-v0-5/378/3 and https://discourse.julialang.org/t/standard-ways-to-run-common-commands/154

[kkmann]

Me too! This would be such a time-saver during development instead of just switching includes on and off by commenting ;)

[PearGod]

Pinging this as it would be very valuable and we're coming up on two years with no activity on it.

[KristofferC]

Issue moved to JuliaLang/Pkg.jl #981 via ZenHub

[StefanKarpinski]

I think GitHub can natively transfer issues now—have you tried it? I'd be curious to see how it works.

[fredrikekre]

have you tried it? I'd be curious to see how it works.

I have, works great, e.g. JuliaLang/Pkg.jl#949 (comment)

[KristofferC]

I never find the button.

[StefanKarpinski]

On the right with all the other things:

[KristofferC]

My GitHub dark scheme is hiding it!