Acid Test: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
==ACID Test for Parsers== | ==ACID Test for Parsers== | ||
This is not really ACID test, but it sounds good. Basically test should run across as many as possible edge cases in | This is not really ACID test, but it sounds good. Basically test should run across as many as possible edge cases in microformats parsing. So far the cases I found are: | ||
* include pattern | * include pattern | ||
* include inside include | * include inside include | ||
* nested µf (agent as vcard inside vcard) | * nested µf (agent as vcard inside vcard) | ||
* multiple | * multiple elements of the same type | ||
* “value” container | * “value” container | ||
* correct work with abbr and img tags | * correct work with abbr and img tags | ||
* tel with type, but without value elements | * tel with type, but without value elements | ||
* tel with type, without | * tel with type, without value, but with “include” | ||
* value as an ul element | * value as an ul element | ||
* “headers” pattern | * “headers” pattern | ||
Line 15: | Line 15: | ||
That’s it so far. You could test your parsers over there: [http://microformatique.com/optimus/test.html] | That’s it so far. You could test your parsers over there: [http://microformatique.com/optimus/test.html] | ||
This thing is under development and will be updated. | |||
==Suggestions== | |||
* Concatenated values (multiple NOTES properties are merged) | |||
* Invalid formats are ignored (missing required properties) | |||
* del element | |||
* rel-tag on categories | |||
* optimizations (FN==ORG, N from FN) | |||
* Multiple sub-properties in ADR and N | |||
* Invalid ISO Dates? |
Latest revision as of 03:26, 24 December 2009
ACID Test for Parsers
This is not really ACID test, but it sounds good. Basically test should run across as many as possible edge cases in microformats parsing. So far the cases I found are:
- include pattern
- include inside include
- nested µf (agent as vcard inside vcard)
- multiple elements of the same type
- “value” container
- correct work with abbr and img tags
- tel with type, but without value elements
- tel with type, without value, but with “include”
- value as an ul element
- “headers” pattern
- “headers” with nested include
That’s it so far. You could test your parsers over there: [1]
This thing is under development and will be updated.
Suggestions
- Concatenated values (multiple NOTES properties are merged)
- Invalid formats are ignored (missing required properties)
- del element
- rel-tag on categories
- optimizations (FN==ORG, N from FN)
- Multiple sub-properties in ADR and N
- Invalid ISO Dates?