-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Separate /test/Project.toml environment file #578
Comments
(If people think this make sense I am happy to do it, however, wanted to check since I think others might know this stuff better than me, and there might be some reason I am unaware of why things are set up as they are) |
Sounds good to me! Our current setup is just historical, based on the older testing style. I agree it would be nice to have a self-contained testing environment one can manually activate. |
Great, will set it up after the updated DSL syntax thing is done. |
Julia 1.10 will probably have functionality making this simpler. So we will hold this off until then: https://discourse.julialang.org/t/link-project-toml-files-or-make-test-prokect-toml-depend-on-main-package-one/93223/3 |
If I get it right, according to
https://pkgdocs.julialang.org/v1/creating-packages/#Test-specific-dependencies-in-Julia-1.2-and-above
the current dogma is to have one Project.toml file for the package in the main folder, and then a separate Project.toml file in /test for which the tests run. Currently, we only have one in the main folder, which has a section
[extras]
to handle test packages.Would it make sense to change to the set up with two different ones? I think one advantage would be that it is easier to activate the test environment to run the tests with the sam environment as CI.
(currently I activate the main one, but that does not provide the packages unique for the tests)
The text was updated successfully, but these errors were encountered: