Inspired by questions on W3C Markdown Community Group.
Pull Requests are welcome. See the CONTRIBUTING Guidelines
Markdown Test Suite already includes tests for many important markdown engines.
To see what the scripts do run:
./cat-all.py -h
./run-tests.py -h
To configure the scripts do:
cp config_local.py.example config_local.py
and edit config_local.py. It is already gitignored.
Sample output from run-tests.py:
gfm |FF.....F.....F...FFFF..F....F........................FFFF...FF...............FF...F.......F...........| 262.88s 102 20 19%
hoedown |..............................F.................................................F.....................| 0.36s 102 2 1%
kramdown |......FFF.....FF.......FF.......FF.FFFFFFFFFFFFF.......................F..............................| 30.69s 102 23 22%
markdown_pl |.....................FFFF...............................F...............F.............................| 2.56s 102 6 5%
marked |..............F.................FFFFFFFFFFFFFFFF......................F.F.............................| 6.22s 102 19 18%
md2html |.........................FFF...F............................................FF........................| 7.42s 102 6 5%
multimarkdown |......FFF....FF...F............FFF.FFFFFFFFFFFFF.....FFFF.........F...................................| 0.58s 102 27 26%
pandoc |FF...........F.F.FFFF..FFFFF....FF.FFFFFFFFFFFFF.....FFFF.....FF............FFF.FFF..................F| 1.11s 102 41 40%
redcarpet |......................................................................................................| 21.49s 102 0 0%
Extensions:
gfm |F.| 2.37s 2 1 50%
hoedown |.| 0.00s 1 0 0%
kramdown |..| 0.62s 2 0 0%
markdown_pl || 0.00s 0 0 0%
marked |F.| 0.13s 2 1 50%
md2html |F.| 0.14s 2 0 0%
multimarkdown |F.| 0.01s 2 1 50%
pandoc |F.| 0.02s 2 1 50%
redcarpet |..| 0.42s 2 0 0%
Where F indicates a failing test.