Markdown Test suites

karlcow · September 3, 2014, 11:58pm

Congratulations on the new specification and work.

Ciro Santilli has built upon something I had started for a Markdown Test Suite. It is a very good work on a comprehensive Test Suite, with a test driver. You can see the test resultsfor something around 16 implementations.

It seems not wise to duplicate the efforts. I’m wondering if we should stop our own effort on this project.

Opinions. What would be the best way forward?

codinghorror · September 4, 2014, 1:45am

I suggest examining the spec and combining any missing tests – tests you created that have no counterpart in the spec – as pull requests. That would be great!

cirosantilli · September 4, 2014, 8:36am

Let’s discontinue Markdown Test Suite, and focus on merging to stmd instead, as it is better on the following points:

the spec is here is way more complete
has two (!) reference implementations
support of major MD players: jgm (pandoc), Atwood (ex-SO), Neil Williams (Reddit), Marti (GitHub)
has a domain name =)

Test quantity / quality is similar.

At a quick look, things that MTS might do better:

tests many implementations in a VM: https://github.com/karlcow/markdown-testsuite/blob/master/Vagrantfile I’m going to propose a caniuse of Markdown in a new topic.
output normalization: we were actually parsing the HTML for the normalizations: https://github.com/karlcow/markdown-testsuite/blob/master/run-tests.py#L20

@codinghorror out of curiosity, was stmd developped quietly and publicized recently, or did I miss an elephant in the room? =) How did it get so much support from the big MD players? Was it @jgm who contacted you guys?

And once again, congrats on this great project.