From aee6d6b5b733aa9bcfa278f8ed8e7c93472c4671 Mon Sep 17 00:00:00 2001 From: David Waern Date: Sun, 22 May 2011 15:41:52 +0000 Subject: Use cabal's test suite support to run the test suite This gives up proper dependency tracking of the test script. --- tests/html-tests/README | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) (limited to 'tests/html-tests/README') diff --git a/tests/html-tests/README b/tests/html-tests/README index fd906b2b..644d0a71 100644 --- a/tests/html-tests/README +++ b/tests/html-tests/README @@ -1,4 +1,3 @@ - This is a testsuite for Haddock that uses the concept of "golden files". That is, it compares output files against a set of reference files. @@ -6,7 +5,7 @@ To add a new test: 1) Create a module in the "tests" directory. - 2) Run runtests.hs. You should now have output/.html. The test + 2) Run "cabal test". You should now have output/.html. The test passes since there is no reference file to compare with. 3) To make a reference file from the output file, do @@ -14,15 +13,12 @@ To add a new test: Tips and tricks: -You can +To copy all output files into reference files, run runhaskell copy.hs -to copy all output files into reference files. - -You can - runhaskell runtests.hs all - -to continue despite a failing test. +You can run all tests despite failing tests, like so + cabal test --test-option=all You can pass extra options to haddock like so - runhaskell runtests.hs --title="All Tests" all + cabal test --test-options='all --title="All Tests"' + -- cgit v1.2.3