Difference between revisions of "test-suite"

From Microformats Wiki
test-suite
Jump to navigation Jump to search
(stub FAQ)
(→‎FAQ: Added paraphrase of JSON vs parsed property comparison)
Line 21: Line 21:
 
== FAQ ==
 
== FAQ ==
 
Frequently asked questions about microformats tests / test suites.
 
Frequently asked questions about microformats tests / test suites.
* ...
+
 
 +
* '''Should we test the whole parser output against a JSON representation of the original data, or compare individual parsed properties?'''
 +
** Paraphrased from [https://github.com/microformats/tests/issues/1 this issue on github]
 +
** Specifically the difficulty is dates/times, where a single datetime can be specified in many different ways, and also represented as an object native to the language the parser is working in.
 +
* …
  
 
== see also ==
 
== see also ==

Revision as of 18:09, 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:

Test Project

On github:

FAQ

Frequently asked questions about microformats tests / test suites.

  • Should we test the whole parser output against a JSON representation of the original data, or compare individual parsed properties?
    • Paraphrased from this issue on github
    • Specifically the difficulty is dates/times, where a single datetime can be specified in many different ways, and also represented as an object native to the language the parser is working in.

see also

previously

Previous microformats1 test suites: Test Suites