aboutsummaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorpaul.rivier <paul.r.ml@gmail.com>2012-04-17 13:14:05 +0200
committerpaul.rivier <paul.r.ml@gmail.com>2012-04-17 13:14:05 +0200
commit411d54ce98f40b5196706804da6167079ed5d824 (patch)
treebb21995ea74e7029b0d8664ca5b0275432407545 /INSTALL
parent5a244bb7b330de981cd1a59330b8e34e159a64e8 (diff)
downloadpandoc-411d54ce98f40b5196706804da6167079ed5d824.tar.gz
Textile reader quick clean-up and added support for LaTeX blocks and inlines.
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