All the Perl that's Practical to Extract and Report
use Perl Log In
Ovid (2709)
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
Satisfaction
Some tests depend on others, thus we number them. If tests break, we fix lower numbered ones first and this frequently takes care of the higher numbered ones.
I think we have finally started really getting the "testing" mindset.
$ perl test_all.pl
01class..............ok
01dbi................ok
02account............ok
02category...........ok
02company............ok
02companyboth........ok
02contact............ok
02country............ok
02customer...........ok
02manf...............ok
02pricelevel.........ok
02pricetypes.........ok
02retailer...........ok
02roletype...........ok
02saleitem...........ok
02saletender.........ok
02session............ok
02states.............ok
02status.............ok
02taxrate............ok
02tendertype.........ok
02term...............ok
02uom................ok
02vendor.............ok
03handlerbase........ok
03pluginhtmltable....ok
03product............ok
03sales..............ok
04completesale.......ok
04handleraccount.....ok
04handlercompany.....ok
04handlercontact.....ok
04handlercustomer....ok
04handlerlogin.......ok
04handlerproduct.....ok
04handlerretailer....ok
04handlertaxrate.....ok
04handlerterms.......ok
All tests successful.
Files=38, Tests=1547, 125 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 CPU)
I'm still not sure why the individual times on the Test::Harness output are zeroes. Plus, when I run tests on my linux box at home, I frequently get many line breaks between lines of output. I was also getting this in Cygwin at work, so it's not just my home 'puter.
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Non-granularity (Score:2)
See my thoughts on this at http://petdance.com/perl/automated-testing/ [petdance.com]
--
xoa
Re:Non-granularity (Score:2)
I guess I wasn't clear. All of the tests do run on their own. Any of those tests programs can be separated from the others and it will work just fine. However, rather than do a bunch of white box unit testing (which is what we were doing) I have found that black box integration testing, while sacrificing some fine-grained control, gets me the results I need.
The higher number tests don't depend on the lower number tests per se, but if a higher level test fails I immediately look for a failure of a lower