Difference between revisions of "hcard-tests"

From Microformats Wiki
hcard-tests
Jump to navigation Jump to search
m
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(17 intermediate revisions by 9 users not shown)
Line 1: Line 1:
= hCard Tests =
+
{{DISPLAYTITLE: hCard tests }}
 +
== newest tests ==
 +
From [[test-suite]]:
 +
* http://ufxtract.com/testsuite/hcard/
 +
* http://ufxtract.com/testsuite/geo/
 +
* ...
  
This page is for documenting [[hcard|hCard]] tests / test cases, both directly, and by reference.
+
== previous mercurial tests ==
 +
The [http://microformats.org/tests/ hcard and hcalendar tests collection] was announced in a [http://microformats.org/discuss/mail/microformats-dev/2006-June/000102.html Jun 7 2006 message] from [http://theryanking.com/ RyanKing].
  
== Test Cases ==
+
They are published at http://microformats.org/tests/hcard/. Each test has an HTML file to parse and a vCard file which describes the hCard data contained in the HTML file.
  
<pre>
+
It's managed in [http://hg.microformats.org/tests/ an hg repository]. [http://www.selenic.com/mercurial/ hg/mercurial] is a distributed revision control system. It can be a little tricky to unlearn cvs habits; there are some good diagrams in [http://www.selenic.com/mercurial/wiki/index.cgi/Presentations?action=AttachFile&do=get&target=google.pdf slides from a 19 Jun talk that Bryan O'Sullivan gave at google]. The [http://www.selenic.com/mercurial/wiki/index.cgi/Presentations mercurial presentations page] also has a link to a 50 minute video.
<span class="vcard>
 
</span>
 
</pre>
 
  
== External Tests ==
+
An [http://hg.microformats.org/x2v/ x2v hg repository] holds code that, by design, passes the tests. [[x2v-issues]] is a place to track issues
 +
in that code.
 +
 
 +
== even older external tests ==
 +
These <span id="External_Tests">external tests</span> have been obsoleted by the above test suites.
  
 
DanConnolly is working on [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest.html]; [http://dev.w3.org/cvsweb/~checkout~/2001/palmagent/hcardTest.html?rev=HEAD&content-type=text/html;%20charset=iso-8859-1 the current version] is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.)
 
DanConnolly is working on [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest.html]; [http://dev.w3.org/cvsweb/~checkout~/2001/palmagent/hcardTest.html?rev=HEAD&content-type=text/html;%20charset=iso-8859-1 the current version] is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.)
 +
 +
MarkPilgrim maintains a series of [http://diveintomark.org/projects/greasemonkey/hcard/tests/ hCard tests] for use with his [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser]
 +
 +
== Related Pages ==
 +
{{hcard-related-pages}}

Latest revision as of 16:26, 18 July 2020

newest tests

From microformats test suites:

previous mercurial tests

The hcard and hcalendar tests collection was announced in a Jun 7 2006 message from RyanKing.

They are published at http://microformats.org/tests/hcard/. Each test has an HTML file to parse and a vCard file which describes the hCard data contained in the HTML file.

It's managed in an hg repository. hg/mercurial is a distributed revision control system. It can be a little tricky to unlearn cvs habits; there are some good diagrams in slides from a 19 Jun talk that Bryan O'Sullivan gave at google. The mercurial presentations page also has a link to a 50 minute video.

An x2v hg repository holds code that, by design, passes the tests. x2v-issues is a place to track issues in that code.

even older external tests

These external tests have been obsoleted by the above test suites.

DanConnolly is working on hcardTest.html; the current version is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.)

MarkPilgrim maintains a series of hCard tests for use with his hCard parser

Related Pages

The hCard specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.