test-suite: Difference between revisions
Jump to navigation
Jump to search
(test-suite moved to test-suite-2009: Pretty much everything here is dated as of 2009, and it makes more sense to start from scratch with a new test-suite page for microformats2 for 2012.) |
(stub from scratch for 2012 with some borrowed prose from before) |
||
| Line 1: | Line 1: | ||
<entry-title>microformats test suites</entry-title> | |||
{{stub}} | |||
Test suites help interoperability and completeness of microformats parsing. This page documents the effort to produce test cases for [[microformats2]] and parsing patterns, so that you can verify the operations of your parser. | |||
==Goals of Test Suite Project== | |||
There's no better way for parser writers to verify the correctness and completeness of their code. | |||
We need to provide a suite to: | |||
* Verify the correctness of [[microformats2-parsing]] | |||
* Indicate the completeness of a [[parser]] implementation | |||
* Ensure that global patterns like [[abbr-design-pattern]] and [[value-class-pattern]] are implemented accurately | |||
* Provide a base set of tests for implementations to build their automated test scripts | |||
* Encourage implementations to put their tests into this combined effort, rather than working alone | |||
== Test Project == | |||
On github: | |||
* https://github.com/microformats/tests | |||
== see also == | |||
* [[microformats2]] | |||
* [[microformats2-parsing]] | |||
== previously == | |||
Previous microformats1 test suites: [[test-suite-2009]] | |||
Revision as of 17:17, 2 December 2012
<entry-title>microformats test suites</entry-title>
This article is a stub. You can help the microformats.org wiki by expanding it.
Test suites help interoperability and completeness of microformats parsing. This page documents the effort to produce test cases for microformats2 and parsing patterns, so that you can verify the operations of your parser.
Goals of Test Suite Project
There's no better way for parser writers to verify the correctness and completeness of their code.
We need to provide a suite to:
- Verify the correctness of microformats2-parsing
- Indicate the completeness of a parser implementation
- Ensure that global patterns like abbr-design-pattern and value-class-pattern are implemented accurately
- Provide a base set of tests for implementations to build their automated test scripts
- Encourage implementations to put their tests into this combined effort, rather than working alone
Test Project
On github:
see also
previously
Previous microformats1 test suites: test-suite-2009