Overhaul pretty-printing in `Testing`
florentc opened this issue · comments
Florent C. commented
The Testing
module invokes the revamped and parameterizable printers for skeletons, mockchain errors, and UTxO state (in the soon to be merged PR #228) but the highest level testing messages are still legacy basic string concatenation from Cooked V1.
It would be interesting to:
- Write better printers that rely on
Prettyprinter
andPrettyCooked
to replace legacy printing such as intestBinaryRelatedBy
ortestOneEquivClass
and convert to string only at the very end usingrenderString
fromCooked.Pretty
- Move actual pretty printing to the
Cooked.Pretty
module or aCooked.Pretty
submodule - Investigate how to tweak Tasty's default output to include additional information (e.g. number of evaluated cooked traces when a test succeeds and nothing would be printed otherwise)
- Investigate if it is possible to render pretty-printed
Doc
elements in Tasty instead of converting toString
(which is now done withrenderString
) to benefit from a rendering that adapts to the terminal size in which the test suite is ran