You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it takes about 10 minutes to test all of flatsurf. That's slowing down development here so we should do something about it.
Profile slow tests
Parallelize tests further, i.e., register (or detect) individual tests (for individual template type arguments) in the Makefile so we can run in parallel with more granularity than just file granularity. (in Apply a Deformation to a Point #303)
Clarify who tests what. E.g., is FlatTriangulation::applyMatrix tested by flat_triangulation.test or by deformation.test? Maybe we should just split the tests up into individual files for the individual methods like FLINT does. What is tested should be indicated cleary by the tags. If something is tested elsewhere, we should just add an empty test that references the other place.
The text was updated successfully, but these errors were encountered:
Since we now run tests fully in parallel this only creates more
confusion. We should instead clearly tag tests to make it clear who
tests what, see flatsurf#313.
saraedum
added a commit
to saraedum/flatsurf
that referenced
this issue
Sep 12, 2022
Currently, it takes about 10 minutes to test all of flatsurf. That's slowing down development here so we should do something about it.
FlatTriangulation::applyMatrix
tested byflat_triangulation.test
or bydeformation.test
?Maybe we should just split the tests up into individual files for the individual methods like FLINT does.What is tested should be indicated cleary by the tags. If something is tested elsewhere, we should just add an empty test that references the other place.The text was updated successfully, but these errors were encountered: