Activate the test env with TestEnv.jl #115
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #115 +/- ##
==========================================
+ Coverage 73.49% 73.61% +0.11%
==========================================
Files 18 18
Lines 1249 1247 -2
==========================================
Hits 918 918
+ Misses 331 329 -2 ☔ View full report in Codecov by Sentry. |
graeme-a-stewart
approved these changes
Jan 29, 2025
|
@all-contributors please add @m-fila for infrastructure, tests |
|
I've put up a pull request to add @m-fila! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up from #114
test/Project.tomlwithProject.toml, and using TestEnv.jl to activate the test environmentTestEnv can be used to programmatically activate a test environment so there is no need to create a separate project for tests.
Running separate files can be done from shell with the main project which I think is quite nice and simple:
The cost of this is that the
TestEnvshould be installed in the default environment, which should be fine since it's small and self-contained, and other packages also suggest using it. Testing with Pkg still works fine without TestEnvAnyway if TestEnv is too much then I can revert to the current solution with
test/Project.tomland propose some changes for it.