Difference between revisions of "test-suite"

From Microformats Wiki
Jump to navigation Jump to search
m (Reverted edits by ABIDEEN0 (Talk) to last version by Tantek)
m (Protected "microformats test suites" [edit=autoconfirmed:move=sysop])
(No difference)

Revision as of 02:03, 3 April 2013

<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:


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 only sometimes represented as an object native to the language the parser is working in. Many microformats / Microformats in HTML5 <time> dates/times/durations are not represented in any native language objects (e.g. month-day). See HTML5 Time element proposals for more variants/details.

see also


Previous microformats1 test suites: Test Suites