On Wed, Apr 6, 2011 at 11:53 PM, Simon Hengel
<simon.hengel@wiktory.org> wrote:
Hello Michael,
> I would like to integrate DocTest into my normal test suite procedures. Do you
> have a recommended approach for this? I think I have projects using all of
> test-framework[1], HTF[2] and hspect[3], so I'm not picky here.
Currently you are pretty much on your own here. A shell script that
runs both, doctest and unit test, is what I currently use.
In principle it should be possible to provide an API function that maps
a list of flags and source files to tests, like:
getDocTests :: [Flag] -> [FilePath] -> IO [Test]
But with this you still have to figure out the flags and source files.
A different approach would be to provide Cabal with a `doctest' target
(similar to the `haddock' target), that runs the DocTests. Cabal
already knows the necessary information to do so.
Sadly, I have no time to work on any of these for at least a month.
Nevertheless, I'd be interested what you think about it.
Cheers,
Simon
I like the idea of a getDocTests function. In theory, it could take a cabal file as an argument, and use the Cabal library to get a list of all modules to be checked. It would also be convenient if it automatically passed in GHC options correlating to each LANGUAGE pragma found on a module.
Michael