It felt a little gross to load up the cradle for the tests of the project that was running them. So I pulled out the cradle code into a separate parse function that we do not call for tests. This also let me bring back the Headless test (normally I wouldn't care this much about headless modules, but stack includes a headless Setup.hs by default).
Theoretically, we could include an entire stack sub project in our testing assets (and maybe a cabal one as well) to test that our cradle code works correctly.
Curious for your thoughts on this @stoeffel!
It felt a little gross to load up the cradle for the tests of the project that was running them. So I pulled out the cradle code into a separate parse function that we do not call for tests. This also let me bring back the Headless test (normally I wouldn't care this much about headless modules, but stack includes a headless
Setup.hsby default).Theoretically, we could include an entire stack sub project in our testing assets (and maybe a cabal one as well) to test that our cradle code works correctly.