Skip to content
Browse files

Updated tap4j site

  • Loading branch information...
1 parent 61deb91 commit 720638849062b8c8313025ed2054a01fe6a6f4e5 @kinow kinow committed Sep 11, 2011
Showing with 26 additions and 1 deletion.
  1. +1 −1 src/site/apt/downloads.apt
  2. +24 −0 src/site/apt/tapdirectives.apt
  3. +1 −0 src/site/site.xml
View
2 src/site/apt/downloads.apt
@@ -12,7 +12,7 @@ Download
<dependency>
<groupid>org.tap4j</groupid>
<artifactid>tap4j</artifactid>
- <version>2.0.3</version>
+ <version>2.0.5</version>
</dependency>
+---+
View
24 src/site/apt/tapdirectives.apt
@@ -0,0 +1,24 @@
+TAP Directives
+
+ Directives are notes that change the meaning of a Test Result. TAP has two
+ directives, SKIP and TODO.
+
+ When a Test Result is marked as SKIP it is counted as having been skipped.
+
+ e.g.: ok 3 - # SKIP Module RPC::XML is not present
+
+ On the other hand, a TODO directive tells the test harness that a Test Result
+ is missing something that will be corrected later.
+
+ e.g.: ok 3 - # TODO install module RPC::XML
+
+ Before version 2.0.5, tap4j Parser ignored lower case skip or todo directives.
+ However after an issue about this was raised in {{{https://wiki.jenkins-ci.org/display/JENKINS/TAP+Plugin}Jenkins TAP Plug-in}} we re-read
+ the specification and checked in {{{http://hexten.net/mailman/listinfo/tap-l}tap-l}} (the TAP mailing list) if it would be
+ correct to use upper and lower case for directives. Now tap4j Parser interprets
+ both lower and upper case directives, i.e., # SKIP or # skip, and # TODO
+ or # todo.
+
+ H.Merijn Brand, Steffen Schwigon and {{{http://overseas-exile.blogspot.com/}Ovid}} contributed with their thoughts
+ on parsing upper and lower case directives in tap-l. Thank you guys.
+
View
1 src/site/site.xml
@@ -28,6 +28,7 @@
<item name="Using TAP with Java book" href="book/"/>
<item name="TAP Consumer" href="tapconsumer.html"/>
<item name="TAP Producer" href="tapproducer.html"/>
+ <item name="TAP Directives" href="tapdirectives.html"/>
</menu>
<menu name="tap4j Extensions">

0 comments on commit 7206388

Please sign in to comment.
Something went wrong with that request. Please try again.