From shlomif at iglu.org.il Sun Mar 9 20:14:40 2008 From: shlomif at iglu.org.il (Shlomi Fish) Date: Sun, 9 Mar 2008 22:14:40 +0200 Subject: [tap-l] TAP, Test::Run and TAP::Parser are now Used for the Anarki Arc Test suite Message-ID: <200803092214.40543.shlomif@iglu.org.il> Hi all! Arc ( http://www.paulgraham.com/arc.html ) is a new dialect of Lisp by Paul Graham and others. There's a community effort to hack on Arc and improve it over at the open Anarki git repository: http://arcfn.com/2008/02/git-and-anarki-arc-repository-brief.html Seeing that a comperhensive test suite was absent, I decided to start writing one. Being involved with the development of Test::Run and other TAP efforts, I naturally decided to use TAP for it, and so I did. This turned out to be a good idea because some of the test programs have been written in Perl. I've written (and later on enhanced) a rudimentary implementation of a TAP emitter in Arc. I also wrote some tests in Perl to test it. The Perl tests use Test::More and Test::Trap ( http://search.cpan.org/dist/Test-Trap/ ). The Arc tests use the TAP emitting library (found in arctap.arc in the repository's root directory). So far the work on the test suite uncovered several bugs in Arc and one bug in Test::Run, and also results in some enhancments to Arc. Plus, I was able to better familiarise myself with Arc, and naturally write test suite code which helps prevents future regressions. I should note that I used Test::Run because of its AlternateInterpreters plugin (which is an idea I originally derived from something Ovid wrote). Currently, my interpreters.conf.yml file reads: <<<<<<<<<< --- - cmd: ./arc.sh pattern: \.arc(?:\.t)?\z type: regex >>>>>>>>>> This uses ./arc.sh to run the tests by default. It's a bit more complicated than that (see Test.sh), but still the Test-Harness-2.54's prove would not do, because it seems the she-bang at the start of the file confuses the Arc implementation. But so far using TAP for the Arc test suite seems like it has been a sound choice. Regards, Shlomi Fish --------------------------------------------------------------------- Shlomi Fish shlomif at iglu.org.il Homepage: http://www.shlomifish.org/ I'm not an actor - I just play one on T.V. From andy at hexten.net Sun Mar 9 22:27:37 2008 From: andy at hexten.net (Andy Armstrong) Date: Sun, 9 Mar 2008 22:27:37 +0000 Subject: [tap-l] TAP, Test::Run and TAP::Parser are now Used for the Anarki Arc Test suite In-Reply-To: <200803092214.40543.shlomif@iglu.org.il> References: <200803092214.40543.shlomif@iglu.org.il> Message-ID: On 9 Mar 2008, at 20:14, Shlomi Fish wrote: > But so far using TAP for the Arc test suite seems like it has been a > sound > choice. Splendid work Shlomi. Please blog this and then post it to reddit. They go crazy for anything about Arc and TAP can hitch a lift on its notoriety :) -- Andy Armstrong, Hexten From schwern at pobox.com Mon Mar 10 17:19:21 2008 From: schwern at pobox.com (Michael G Schwern) Date: Mon, 10 Mar 2008 10:19:21 -0700 Subject: [tap-l] SKIP_ALL tests should not get hidden In-Reply-To: References: <166662.31668.qm@web60815.mail.yahoo.com> <155AA7B6-809C-4339-B56A-FADB09E21412@hexten.net> <4743702C.90308@pobox.com> Message-ID: <47D56D99.5010000@pobox.com> Andy Armstrong wrote: > On 20 Nov 2007, at 23:39, Michael G Schwern wrote: >>> Do we like that? >> >> Test::Harness 2 put it on it's own line mostly to avoid wrapping off >> the right >> side of the screen. I still lean in that direction. > > Hmm. I'm kind of hooked on the new behaviour now. It puts a summary > column right where I can find it. Maybe this is one of those 80 columns vs 120 columns things, but let's compare. Here's the Test::More suite with TH 2.64. t/00test_harness_check..........ok t/bad_plan......................ok t/bail_out......................ok t/BEGIN_require_ok..............ok t/BEGIN_use_ok..................ok t/buffer........................ok t/Builder.......................ok t/carp..........................ok t/circular_data.................ok t/cmp_ok........................ok t/create........................ok t/curr_test.....................ok t/details.......................ok t/diag..........................ok t/dont_overwrite_die_handler....ok t/eq_set........................ok t/exit..........................ok t/extra.........................ok t/extra_one.....................ok t/fail-like.....................ok t/fail-more.....................ok t/fail..........................ok t/fail_one......................ok t/filehandles...................ok t/fork..........................ok t/harness_active................ok t/has_plan......................ok t/has_plan2.....................ok t/import........................ok t/is_deeply_dne_bug.............ok t/is_deeply_fail................ok t/is_deeply_with_threads........skipped all skipped: many perls have broken threads. Enable with AUTHOR_TESTING. t/is_fh.........................ok t/maybe_regex...................ok 3/16 skipped: various reasons t/missing.......................ok t/More..........................ok t/no_diag.......................ok t/no_ending.....................ok t/no_header.....................ok t/no_plan.......................ok t/ok_obj........................ok t/output........................ok t/overload......................ok t/overload_threads..............ok 1/5 skipped: various reasons t/plan..........................ok t/plan_bad......................ok t/plan_is_noplan................ok t/plan_no_plan..................ok 1/6 skipped: various reasons t/plan_shouldnt_import..........ok t/plan_skip_all.................skipped all skipped: Just testing plan & skip_all t/pod-coverage..................ok t/pod...........................ok t/require_ok....................ok t/reset.........................ok t/simple........................ok t/skip..........................ok 8/17 skipped: various reasons t/skipall.......................ok t/strays........................skipped all skipped: not completed t/tbm_doesnt_set_exported_to....ok t/tbt_01basic...................ok t/tbt_02fhrestore...............ok t/tbt_03die.....................ok t/tbt_04line_num................ok t/tbt_05faildiag................ok t/tbt_06errormess...............ok t/tbt_07args....................ok t/thread_taint..................ok t/threads.......................ok t/todo..........................ok t/try...........................ok t/undef.........................ok t/use_ok........................ok t/useing........................ok t/utf8..........................ok 2/5 skipped: various reasons All tests successful, 3 tests and 15 subtests skipped. And here it is with 3.10. t/00test_harness_check............ok t/bad_plan........................ok t/bail_out........................ok t/BEGIN_require_ok................ok t/BEGIN_use_ok....................ok t/buffer..........................ok t/Builder.........................ok t/carp............................ok t/circular_data...................ok t/cmp_ok..........................ok t/create..........................ok t/curr_test.......................ok t/details.........................ok t/diag............................ok t/dont_overwrite_die_handler......ok t/eq_set..........................ok t/exit............................ok t/extra...........................ok t/extra_one.......................ok t/fail-like.......................ok t/fail-more.......................ok t/fail............................ok t/fail_one........................ok t/filehandles.....................ok t/fork............................ok t/harness_active..................ok t/has_plan........................ok t/has_plan2.......................ok t/import..........................ok t/is_deeply_dne_bug...............ok t/is_deeply_fail..................ok t/is_deeply_with_threads..........skipped: many perls have broken threads. Enable with AUTHOR_TESTING. t/is_fh...........................ok t/maybe_regex.....................ok t/missing.........................ok t/More............................ok t/no_diag.........................ok t/no_ending.......................ok t/no_header.......................ok t/no_plan.........................ok t/ok_obj..........................ok t/output..........................ok t/overload........................ok t/overload_threads................ok t/plan............................ok t/plan_bad........................ok t/plan_is_noplan..................ok t/plan_no_plan....................ok t/plan_shouldnt_import............ok t/plan_skip_all...................skipped: Just testing plan & skip_all t/pod-coverage....................ok t/pod.............................ok t/require_ok......................ok t/reset...........................ok t/simple..........................ok t/skip............................ok t/skipall.........................ok t/strays..........................skipped: not completed t/tbm_doesnt_set_exported_to......ok t/tbt_01basic.....................ok t/tbt_02fhrestore.................ok t/tbt_03die.......................ok t/tbt_04line_num..................ok t/tbt_05faildiag..................ok t/tbt_06errormess.................ok t/tbt_07args......................ok t/thread_taint....................ok t/threads.........................ok t/todo............................ok t/try.............................ok t/undef...........................ok t/use_ok..........................ok t/useing..........................ok t/utf8............................ok All tests successful. Files=74, Tests=540, 4 wallclock secs ( 0.32 usr 0.36 sys + 2.80 cusr 0.93 csys = 4.41 CPU) Result: PASS One of the immediate differences is that TH 3 isn't nearly as chatty about individual skipped tests, which I like. But as you can see, the skip message of t/is_deeply_with_threads.t wraps off the right side. TH 2 does as well, but at least there's a bit more room. One of the issues I was always fighting with TH 2's formatting was trying to cram everything into one line. Moving directive information onto it's own line eased that. -- package Outer::Space; use Test::More tests => 9; From shlomif at iglu.org.il Mon Mar 10 20:03:19 2008 From: shlomif at iglu.org.il (Shlomi Fish) Date: Mon, 10 Mar 2008 22:03:19 +0200 Subject: [tap-l] TAP, Test::Run and TAP::Parser are now Used for the Anarki Arc Test suite In-Reply-To: References: <200803092214.40543.shlomif@iglu.org.il> Message-ID: <200803102203.20277.shlomif@iglu.org.il> On Monday 10 March 2008, Andy Armstrong wrote: > On 9 Mar 2008, at 20:14, Shlomi Fish wrote: > > But so far using TAP for the Arc test suite seems like it has been a > > sound > > choice. > > Splendid work Shlomi. Please blog this and then post it to reddit. > They go crazy for anything about Arc and TAP can hitch a lift on its > notoriety :) Thanks for the advice. I did that: http://reddit.com/info/6bk9t/comments/ Please moderate it up if you have a reddit account. Regards, Shlomi Fish --------------------------------------------------------------------- Shlomi Fish shlomif at iglu.org.il Homepage: http://www.shlomifish.org/ I'm not an actor - I just play one on T.V. From andy at hexten.net Mon Mar 10 20:10:33 2008 From: andy at hexten.net (Andy Armstrong) Date: Mon, 10 Mar 2008 20:10:33 +0000 Subject: [tap-l] TAP, Test::Run and TAP::Parser are now Used for the Anarki Arc Test suite In-Reply-To: <200803102203.20277.shlomif@iglu.org.il> References: <200803092214.40543.shlomif@iglu.org.il> <200803102203.20277.shlomif@iglu.org.il> Message-ID: On 10 Mar 2008, at 20:03, Shlomi Fish wrote: > Thanks for the advice. I did that: > > http://reddit.com/info/6bk9t/comments/ > > Please moderate it up if you have a reddit account. Done :) -- Andy Armstrong, Hexten From jeremiah.foster at ericsson.com Wed Mar 19 16:34:06 2008 From: jeremiah.foster at ericsson.com (Jeremiah C. Foster) Date: Wed, 19 Mar 2008 17:34:06 +0100 Subject: [tap-l] Outputting TAP from the shell Message-ID: <1205944446.5608.20.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> Hello! I have read a bit on the TAP wiki about various ways to output TAP. In particular I would like to output TAP so that I can read it with TAP::Parser::Aggregator. I have a set of scripts written in Tcl (i.e. expect), perl and shell script. I would like to emit TAP from the shell scripts. I looked at the git project's test scripts, and stole some code to print out ok and fail, but I see no way to present to the TAP::Parser::Aggregator module information about the number of tests passed. Is there an example of this somewhere written in shell? Lacking an example, what do I have to pass to TAP::Parser::Aggregator so that I can get an aggregate of passed and failed tests? Here is a sample of my output: 080319 2008 007.02.sh: ok 1 - linux-logtest.x86_64.rpm on 192.168.0.5 080319 2008 007.02.sh: ok 2 - linux-logtest.x86_64.rpm to 192.168.0.5 080319 2008 007.02.sh: FAIL 3 - linux-logtest.x86_64.rpm not moved! 080319 2008 007.02.sh: ok 4 - linux-logtest.x86_64.rpm on 192.168.0.5 Passed: 0 Failed: 0 As you can see, I can output fail and ok, but it does not get aggregated. Any pointers welcome! Thanks, Jeremiah From publiustemp-tapx at yahoo.com Thu Mar 20 13:30:37 2008 From: publiustemp-tapx at yahoo.com (Ovid) Date: Thu, 20 Mar 2008 06:30:37 -0700 (PDT) Subject: [tap-l] Outputting TAP from the shell In-Reply-To: <1205944446.5608.20.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> Message-ID: <975357.43064.qm@web65701.mail.ac4.yahoo.com> --- "Jeremiah C. Foster" wrote: > Hello! > > I have read a bit on the TAP wiki about various ways to output TAP. > In > particular I would like to output TAP so that I can read it with > TAP::Parser::Aggregator. I have a set of scripts written in Tcl (i.e. > expect), perl and shell script. I would like to emit TAP from the > shell > scripts. > > I looked at the git project's test scripts, and stole some code to > print out ok and fail, but I see no way to present to the > TAP::Parser::Aggregator module information about the number of tests > passed. Is there an example of this somewhere written in shell? > Lacking > an example, what do I have to pass to TAP::Parser::Aggregator so that > I > can get an aggregate of passed and failed tests? > > Here is a sample of my output: > > 080319 2008 007.02.sh: ok 1 - linux-logtest.x86_64.rpm on > 192.168.0.5 > 080319 2008 007.02.sh: ok 2 - linux-logtest.x86_64.rpm to > 192.168.0.5 > 080319 2008 007.02.sh: FAIL 3 - linux-logtest.x86_64.rpm not > moved! > 080319 2008 007.02.sh: ok 4 - linux-logtest.x86_64.rpm on > 192.168.0.5 > Passed: 0 > Failed: 0 > > > As you can see, I can output fail and ok, but it does not get > aggregated. Any pointers welcome! The ok/not ok bit must be at the start of each line (also note that I have 'not ok' instead of 'FAIL'): ok 1 - linux-logtest.x86_64.rpm on 192.168.0.5 ok 2 - linux-logtest.x86_64.rpm to 192.168.0.5 not ok 3 - linux-logtest.x86_64.rpm not moved! ok 4 - linux-logtest.x86_64.rpm on 192.168.0.5 Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/ From jeremiah.foster at ericsson.com Thu Mar 20 14:07:05 2008 From: jeremiah.foster at ericsson.com (Jeremiah C. Foster) Date: Thu, 20 Mar 2008 15:07:05 +0100 Subject: [tap-l] Outputting TAP from the shell In-Reply-To: <975357.43064.qm@web65701.mail.ac4.yahoo.com> References: <975357.43064.qm@web65701.mail.ac4.yahoo.com> Message-ID: <1206022025.5854.10.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> On Thu, 2008-03-20 at 06:30 -0700, Ovid wrote: > --- "Jeremiah C. Foster" wrote: > > what do I have to pass to TAP::Parser::Aggregator so that > > I > > can get an aggregate of passed and failed tests? > > > > Here is a sample of my output: > > > > 080319 2008 007.02.sh: ok 1 - linux-logtest.x86_64.rpm on > > 192.168.0.5 > > 080319 2008 007.02.sh: ok 2 - linux-logtest.x86_64.rpm to > > 192.168.0.5 > > 080319 2008 007.02.sh: FAIL 3 - linux-logtest.x86_64.rpm not > > moved! > > 080319 2008 007.02.sh: ok 4 - linux-logtest.x86_64.rpm on > > 192.168.0.5 > > Passed: 0 > > Failed: 0 > > > > > > As you can see, I can output fail and ok, but it does not get > > aggregated. Any pointers welcome! > > The ok/not ok bit must be at the start of each line (also note that I > have 'not ok' instead of 'FAIL'): > > ok 1 - linux-logtest.x86_64.rpm on 192.168.0.5 > ok 2 - linux-logtest.x86_64.rpm to 192.168.0.5 > not ok 3 - linux-logtest.x86_64.rpm not moved! > ok 4 - linux-logtest.x86_64.rpm on 192.168.0.5 Thanks Ovid! That worked like a charm. Jeremiah From patrick.leboutillier at gmail.com Thu Mar 20 19:57:50 2008 From: patrick.leboutillier at gmail.com (Patrick LeBoutillier) Date: Thu, 20 Mar 2008 15:57:50 -0400 Subject: [tap-l] Outputting TAP from the shell In-Reply-To: <1205944446.5608.20.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> References: <1205944446.5608.20.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> Message-ID: Hi all, A while back I ported libtap to Java (I called it JTap: http://testanything.org/wiki/index.php/JTap). I was looking at it earlier today after following this thread and was thinking I might try to port it to bash (it would really just be a batch of functions with a few globals, nothing too fancy). Would anyone be interested? Patrick On Wed, Mar 19, 2008 at 12:34 PM, Jeremiah C. Foster wrote: > Hello! > > I have read a bit on the TAP wiki about various ways to output TAP. In > particular I would like to output TAP so that I can read it with > TAP::Parser::Aggregator. I have a set of scripts written in Tcl (i.e. > expect), perl and shell script. I would like to emit TAP from the shell > scripts. > > I looked at the git project's test scripts, and stole some code to > print out ok and fail, but I see no way to present to the > TAP::Parser::Aggregator module information about the number of tests > passed. Is there an example of this somewhere written in shell? Lacking > an example, what do I have to pass to TAP::Parser::Aggregator so that I > can get an aggregate of passed and failed tests? > > Here is a sample of my output: > > 080319 2008 007.02.sh: ok 1 - linux-logtest.x86_64.rpm on 192.168.0.5 > 080319 2008 007.02.sh: ok 2 - linux-logtest.x86_64.rpm to 192.168.0.5 > 080319 2008 007.02.sh: FAIL 3 - linux-logtest.x86_64.rpm not moved! > 080319 2008 007.02.sh: ok 4 - linux-logtest.x86_64.rpm on 192.168.0.5 > Passed: 0 > Failed: 0 > > > As you can see, I can output fail and ok, but it does not get > aggregated. Any pointers welcome! > > Thanks, > > Jeremiah > > > > _______________________________________________ > tap-l mailing list > tap-l at testanything.org > http://testanything.org/mailman/listinfo/tap-l > -- ===================== Patrick LeBoutillier Laval, Qu?bec, Canada From andy at hexten.net Thu Mar 20 20:26:27 2008 From: andy at hexten.net (Andy Armstrong) Date: Thu, 20 Mar 2008 20:26:27 +0000 Subject: [tap-l] Outputting TAP from the shell In-Reply-To: References: <1205944446.5608.20.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> Message-ID: <52F5A49A-81FE-42FB-8BB5-E44EF970C8A4@hexten.net> On 20 Mar 2008, at 19:57, Patrick LeBoutillier wrote: > Hi all, > > A while back I ported libtap to Java (I called it JTap: > http://testanything.org/wiki/index.php/JTap). > I was looking at it earlier today after following this thread and was > thinking I might try to port it to bash (it would really just be a > batch of functions with a few globals, nothing too fancy). > > Would anyone be interested? It would certainly make it accessible to people who don't know Perl - which is a good thing. I'd say go for it. -- Andy Armstrong, Hexten From patl at cpan.org Tue Mar 25 17:40:34 2008 From: patl at cpan.org (Patrick LeBoutillier) Date: Tue, 25 Mar 2008 13:40:34 -0400 Subject: [tap-l] Outputting TAP from the shell In-Reply-To: <52F5A49A-81FE-42FB-8BB5-E44EF970C8A4@hexten.net> References: <1205944446.5608.20.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> <52F5A49A-81FE-42FB-8BB5-E44EF970C8A4@hexten.net> Message-ID: Hi all, I published a small BASH library that outputs TAP. I called it 'tap-functions' and it's modeled after libtap/JTap. All the details are here in the TAP wiki: http://testanything.org/wiki/index.php/Tap-functions Usage is pretty basic, the only thing that needs some getting used to is the fact that functions that expect boolean values, like 'ok' and 'skip', take 0 to mean success and everything else to mean false (in accordance with the usual shell script logic). I have performed basic testing and it looks pretty good, but if anyone has the time to try it out to see how useable it is that'd be great. As usual all comments/suggestions are welcome. Cheers, Patrick On Thu, Mar 20, 2008 at 4:26 PM, Andy Armstrong wrote: > On 20 Mar 2008, at 19:57, Patrick LeBoutillier wrote: > > Hi all, > > > > A while back I ported libtap to Java (I called it JTap: > > http://testanything.org/wiki/index.php/JTap). > > I was looking at it earlier today after following this thread and was > > thinking I might try to port it to bash (it would really just be a > > batch of functions with a few globals, nothing too fancy). > > > > Would anyone be interested? > > > It would certainly make it accessible to people who don't know Perl - > which is a good thing. I'd say go for it. > > -- > Andy Armstrong, Hexten > > > > > > > _______________________________________________ > tap-l mailing list > tap-l at testanything.org > http://testanything.org/mailman/listinfo/tap-l > -- ===================== Patrick LeBoutillier Laval, Qu?bec, Canada From jeremiah.foster at ericsson.com Wed Mar 26 08:34:18 2008 From: jeremiah.foster at ericsson.com (Jeremiah C. Foster) Date: Wed, 26 Mar 2008 09:34:18 +0100 Subject: [tap-l] Outputting TAP from the shell In-Reply-To: References: <1205944446.5608.20.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> <52F5A49A-81FE-42FB-8BB5-E44EF970C8A4@hexten.net> Message-ID: <1206520458.9945.5.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> Hello Patrick and everyone else, I am doing some testing using bash and perl (and even expect, yuck.) I will use your library and test it out. I have stolen some stuff from the git project and written some stuff of my own so I may have a bit of a NIH syndrome. Also, I proposed to brian d. foy an article on TAP for The Perl Journal (it would be an article for those new to TAP). Is it okay to post parts of it to this list for expert commentary? Many thanks, Jeremiah On Tue, 2008-03-25 at 13:40 -0400, Patrick LeBoutillier wrote: > Hi all, > > I published a small BASH library that outputs TAP. I called it > 'tap-functions' and it's modeled after libtap/JTap. > All the details are here in the TAP wiki: > http://testanything.org/wiki/index.php/Tap-functions > > Usage is pretty basic, the only thing that needs some getting used to > is the fact that functions that expect boolean values, like 'ok' and > 'skip', take 0 to mean success and everything else to mean false (in > accordance with the usual shell script logic). > > I have performed basic testing and it looks pretty good, but if anyone > has the time to try it out to see how useable it is that'd be great. > As usual all comments/suggestions are welcome. > > > Cheers, > > Patrick > > > > It would certainly make it accessible to people who don't know Perl - > > which is a good thing. I'd say go for it. > > > > -- > > Andy Armstrong, Hexten From publiustemp-tapx at yahoo.com Wed Mar 26 09:50:40 2008 From: publiustemp-tapx at yahoo.com (Ovid) Date: Wed, 26 Mar 2008 02:50:40 -0700 (PDT) Subject: [tap-l] Outputting TAP from the shell In-Reply-To: <1206520458.9945.5.camel@seasc0551.dyn.rnd.as.sw.ericsson.se> Message-ID: <658938.29339.qm@web65703.mail.ac4.yahoo.com> --- "Jeremiah C. Foster" wrote: > Also, I proposed to brian d. foy an article on TAP for The Perl > Journal > (it would be an article for those new to TAP). Is it okay to post > parts > of it to this list for expert commentary? I don't mind. It would be good to ensure that the TAP information getting out there is as accurate as possible. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/ From pagaltzis at gmx.de Sat Mar 29 11:32:11 2008 From: pagaltzis at gmx.de (Aristotle Pagaltzis) Date: Sat, 29 Mar 2008 12:32:11 +0100 Subject: [tap-l] MySQL + TAP == MyTAP In-Reply-To: <47EE18B6.9040901@pobox.com> References: <47EE18B6.9040901@pobox.com> Message-ID: <20080329113211.GZ22144@klangraum> Hi Michael, * Michael G Schwern [2008-03-29 11:35]: > Stumbled across this while finding an alternative to libtap for > testing C (it has some sort of issue linking with this hairy > project I'm working on). Apparently MySQL wrote their own TAP > library for C. > > From http://dev.mysql.com/doc/mysqltest/en/unit-test.html > > The unit-testing facility is based on the Test Anything > Protocol (TAP) which is mainly used when developing Perl and > PHP modules. To write unit tests for C/C++ code, MySQL has > developed a library for generating TAP output from C/C++ files. > Each unit test is written as a separate source file that is > compiled to produce an executable. For the unit test to be > recognized as a unit test, the executable file has to be of the > format mytext-t. For example, you can create a source file > named mytest-t.c the compiles to produce an executable > mytest-t. The executable will be found and run when you execute > make test or make test-unit in the distribution top-level > directory. > > Here's the docs. http://www.kindahl.net/mytap/doc/index.html I think you wanted to send this to the TAP list. :-) Regards, -- Aristotle Pagaltzis //