-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Labels
Description
The current unit testing structure was aimed mainly at testing all possible combinations {f, G, IA}
where f
is the integral function name/alias, G
is a Meshes.Geometry
sub-type, and IA
is an integration algorithm. In hindsight, the system I wrote for batching these tests was perhaps a little bit too clever for its own good. It also relies on Meshes.measure
to produce correct answers for a unit-valued integrand.
As of 7-Sep-2024, we’re currently at about 77% code coverage per the Codecov report. Most of the gaps seem to be related to wrapper/convenience methods, i.e. ones that simply batch out to the core integration methods.
Ideas for a more robust test system:
- Define more interesting test geometries with analytic solutions to check against
- Evaluate whether TestItems.jl could be helpful here (edit: complete, update below)
Status of Unit Tests with Analytic Solutions
-
Ball
(2D) -
Ball
(3D) -
BezierCurve
-
Box
(1D) -
Box
(2D) -
Box
(3D) -
Box
(4D) -
CartesianGrid
-
Circle
-
Cylinder
-
CylinderSurface
-
Disk
-
Ellipsoid
-
Hexahedron
-
Line
-
ParametrizedCurve
-
Plane
-
PolyArea
-
Quadrangle
-
Ray
-
RegularGrid
-
Ring
-
Rope
-
Segment
-
SimpleMesh
-
Sphere
(2D) -
Sphere
(3D) -
StructuredMesh
-
Tetrahedron
-
Torus
-
Triangle
-
Wedge
-
Cone
-
ConeSurface
-
Frustum
-
FrustumSurface
-
ParaboloidSurface
-
Pyramid