-
Notifications
You must be signed in to change notification settings - Fork 5
Switch to TestItems.jl #77
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
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #77 +/- ##
==========================================
- Coverage 94.70% 94.01% -0.70%
==========================================
Files 11 11
Lines 737 935 +198
==========================================
+ Hits 698 879 +181
- Misses 39 56 +17
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Ugh, Windows. Will take a look Update: Welp, looks to be an inference issue specific to Julia v1.6. Side request, can we start dropping support for old Julia versions and swap to LTS (v1.10) instead 😅 I am curious though why this issue only shows itself when switching to this testing framework |
Fixed a type instability I accidentally introduced. Seemed to do the trick (update: plus bumping oldest supported version to LTS). Looks like the last thing is something like this for nightly julia-vscode/TestItemRunner.jl#114. I don't think this should hold up the PR, especially if we end up going with something like JuliaAstro/JuliaAstro.github.io#157, so will go ahead merge after other tests complete |
codecov decrease looks to be mostly noise, will go ahead and merge |
Hey all, I've been noodling around with different test frameworks lately and have been liking TestItems.jl. Its filtering capabilities are pretty convenient, and I've found myself reaching for it when wanting to quickly test something in other PRs, e.g.,
I also like how they take a page out of Rust's book and allow for source code and tests to be located in the same file, but I know that's more a matter of personal taste
I'm not a VS Code user, but I've heard it's pretty nice for that too, which could potentially help to further reduce contributor friction
At any rate, I was wondering what folks thought about transitioning to this framework here, and if there are any trade-offs to consider
Thanks!