On Mon, Feb 21, 2005 at 12:29:59PM -0000, Clayton, Nik wrote: > Perhaps a gammar (or just a regex) that describes a fully conforming test > line would be helpful. > > Some comments about POSIX (non-)conformance might be useful, see the DejaGnu > docs for examples; http://www.gnu.org/software/dejagnu/manual/x47.html.
As we don't have a copy of POSIX 1003.3 I don't know if we can really say anything except perhaps "conformance with POSIX 1003.3 standard for test frameworks was not considered in the formation of TAP" or something to express that we haven't looked at the POSIX standard. >From what I can scrape from the POSIX docs, we have equivalents to... PASS == ok FAIL == not ok XFAIL == ok # TODO (not POSIX but dejagnu) UNRESOLVED == Bail out! and perhaps a non-zero exit code. UNTESTED == ok # TODO & SKIP UNSUPPORTED == ok # SKIP Instead of just having a POSIX non-compliance section it might be worthwhile having a comparision to other testing systems section, including Dejagnu, POSIX and JUnit, drawing analogies between them and TAP. It would help those who are already familiar with other systems to more easily understand TAP. PS is TODO & SKIP mentioned in TAP?
