However, we're not actually running these doctests (using doctest-parallel, or cabal-docspec, etc) in an automated fashion.
So let's either:
Enable doctests in tzbot. Beware making cabal-docspec play ball with nix is not a trivial task - but we did manage to get it working in morley, so maybe we could reuse that.
Alternatively, move the tests to tzbot-test and rewrite them using tasty
Or do both :D
Acceptance criteria
We have tests for the parser being run in the pipeline.
Clarification and motivation
Right now, we have some tests for the parser written using doctests.
However, we're not actually running these doctests (using
doctest-parallel, orcabal-docspec, etc) in an automated fashion.So let's either:
tzbot. Beware makingcabal-docspecplay ball with nix is not a trivial task - but we did manage to get it working inmorley, so maybe we could reuse that.tzbot-testand rewrite them using tastyAcceptance criteria