-
Notifications
You must be signed in to change notification settings - Fork 4
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
Complete transition away from auto-tests #100
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #100 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 17 17
Lines 258 258
=========================================
Hits 258 258 ☔ View full report in Codecov by Sentry. |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
I'm temporarily re-marking this as draft. I'm just going to go ahead and finish converting the remaining |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This looks pretty good. In my opinion, we can keep one file for now. The file auto_tests.jl can be deleted now, can't it? Testing more interesting integrand functions would definitely be good. |
Co-authored-by: Joshua Lampert <[email protected]>
Thanks! Part of me prefers the reduced code redundancy of the auto-test system, but this longer form is also much less complex to debug, and will allow for individualized rule settings and non-unit integrands for everything with time. For now, I didn’t want the lack of analytic solutions to keep holding up the transition.
Yes. I was planning to delete it once we’re comfortable that all CI is passing and that those tests are officially dead. |
Tests look good. |
I'm away from my PC right now so can't |
I removed the file in 2fb6d2b. |
Changes
auto-tests.jl
) to new-style tests (combinations.jl
), progressing toward completion of Need unit tests with analytic solutions #67Ball
in 2DBall
in 3DCircle
Cylinder
CylinderSurface
Disk
ParaboloidSurface
Sphere
in 2DSphere
in 3DTetrahedron
Torus
Triangle
Future Work/Considerations
This PR will get
combinations.jl
up to around 800 lines. Should this file be partitioned into multiple files? One per geometry type? Separate file for geometries covered byspecializations
?These new tests replicate the old methodology of using a unit integrand with
Meshes.measure
as a reference solution. More interesting integrand functions and test geometries would be nice in the longer term.