- Output type could be implied from
a/@typerather than explicit?. Currently the output type is explicit in a
typeattribute, but either the output could just be taken from the anchor, or if it is duplicated visibly, perhaps it should match the MIME type rather than using strings? e.g.
Difference between revisions of "test-fixture-issues"
Jump to navigation Jump to search
(Documented test-fixture suggestions we might consider before putting into production.)
Revision as of 21:25, 29 June 2009
Issues against test-fixture. Note that this poshformat has not been through the microformats process and serves a funcational purpose for the microformats test suites work.
- Represent history of changes using hAtom rather than hCalendar. It strikes me that hAtom 0.1 would be a more appropriate format for a changelog than hCalendar.
- Consider separating *Unit asserts from custom asserts. Although the normalisation of Geo and Dates is a very useful enhancement, they may not be essential (since ISO dates can be compared somewhat reliably as strings, and co-ordinates compared to the same precision as they appear in the source). This seems desirable for simple conversion into something like JUnit, without being dependent on additional functions.