Re:The Future of Markdown
by mistercow on Friday October 26, 2012 @03:13AM
(#4701199)
I'm confused. How are you supposed to have a conformance test without first having a spec? To what would the implementations be conforming, if not a spec?
[ Parent
| on HN ]
Sorry, What I meant to really say is specs are not sufficient. Sure specs are important. But even with specs, without comprehensive conformance tests implementations will diverge.
I work on the WebGL spec and tests based off the OpenGL ES spec and tests. Even though the OpenGL ES spec is long and detailed, every edge case for which there is no test is broken or different in one driver or another.
In an ideal world, the spec would be the test. A spec is just a human readable test. A test is just a machine readable spec.
Re:The Future of Markdown
by ZeroGravitas on Friday October 26, 2012 @07:29AM
(#4701741)
It's entirely possible to build a conformance test suite around an existing 'black box' of code and accept that whatever it does, even stuff that might be considered a bug, is what any compliant implementation should also do.
(You could also fix some of the more egregious bugs, and then expect implementations to follow your new behaviour)