You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSCode test running follows this simple rule: for each @testitem we look in the folder, then in the parent folder etc until we find a Project.toml that defines a package, and then the @testitem is part of that package.
The TestItemRunner.jl implementation doesn't follow that philosophy fully, I think what is missing there is that we should by default skip any child folder that has a new Project.toml in it that defines a new package. So in @NHDaly's tree, if someone runs test/runtests.jl, then that should actually not run the @testitems of the sub packages, right?
VSCode test running follows this simple rule: for each
@testitem
we look in the folder, then in the parent folder etc until we find aProject.toml
that defines a package, and then the@testitem
is part of that package.The TestItemRunner.jl implementation doesn't follow that philosophy fully, I think what is missing there is that we should by default skip any child folder that has a new
Project.toml
in it that defines a new package. So in @NHDaly's tree, if someone runstest/runtests.jl
, then that should actually not run the@testitem
s of the sub packages, right?Originally posted by @davidanthoff in #39 (comment)
The text was updated successfully, but these errors were encountered: