summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2012-04-27 15:00:02 -0700
committerJohn MacFarlane <jgm@berkeley.edu>2012-04-27 15:00:02 -0700
commit4b77def06173cd9a134c83aba5a0b1758b3b91fc (patch)
treedc8a1d3df095f5e5a6183dff4d3509c589995bcf /INSTALL
parent77125ea68c4c59285a02275f592eb5d41dd3e840 (diff)
parent7b111542c0ef62802a65986b41829196510e5b3e (diff)
Merge pull request #485 from paul-r-ml/master
Textile reader update
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL22
1 files changed, 22 insertions, 0 deletions
diff --git a/INSTALL b/INSTALL
index 7a63989c5..4e08a382b 100644
--- a/INSTALL
+++ b/INSTALL
@@ -130,3 +130,25 @@ This is essentially what the binary installer does.
[blaze-html]: http://hackage.haskell.org/package/blaze-html
[Cabal User's Guide]: http://www.haskell.org/cabal/release/latest/doc/users-guide/builders.html#setup-configure-paths
+
+Running tests
+-------------
+
+Pandoc comes with an automated test suite integrated to cabal. Data
+files are located under the 'tests' directory. If you implement a new
+feature, please update them to improve covering, and make sure by any
+necessary mean that the new reference native file is 100% correct.
+
+Also, tests require templates that leave in a separate git repository,
+tied into the main one as a git submodule. To populate 'template'
+directory, you must therefore run first :
+
+ git submodule update --init templates
+
+You are now ready to build tests :
+
+ cabal-dev install -ftests
+
+And finally run them !
+
+ cabal-dev test