pkgsrc changes:
- Adjusting license definition
- Adjusting dependencies according to META.yml (choosing the higher
versions in case of duplicated entries)
Upstream changes:
0.361 20/10/2009
- Keep Makefile.PL in synch.
0.36 18/10/2009
- Mark for production.
- Removed 'dump.t' files in tests.
- Improve Test::Aggregate::Nested docs.
- Removed some dead code.
- Suppress multiple plans (#48352, Chisel Wright)
0.35_07 19/08/2009
- Added missing files to MANIFEST.
0.35_06 28/06/2009
- Added support for nested TAP via Test::Aggregate::Nested.
- I really, really need to get a real release out.
0.35_05 20/05/2009
- Removed bogus test file throwing my counts off. No wonder all tests
were failing for people!
- Remove development lib links.
0.35_04 Unreleased.
- Unlink dump files in tests.
0.35_03 15/05/2009
- Don't run done_testing() in tests if it doesn't exist.
0.35_02 14/05/2009
- Deprecate tests run in BEGIN/END/CHECK/INIT.
See http://use.perl.org/~Ovid/journal/38974 for more information.
- check_plan, if set, is now done at the end of each test instead of
the end of all tests.
- Make it work with the Test::Builder 0.88 and previous versions.
- Embed the calling test script name in a comment at the top of the
dump file.
- Fix a doc typo (thanks to Offer Kaye for the report)
- Cleaned up some tests.
0.35_01 18/11/2008
- Make 'exit()' scream loudly if called.
- Move Test::Aggregate::Builder globals into a hashref in the object.
Further encapsulation to come later.
- Export &run_this_test_program from Test::Aggregate to make dump
files cleaner.
- Reorganize the test suite to avoid false negatives.
dependency for the update of Catalyst::Runtime (/www/p5-Catalyst-Runtime)
to 5.800.
A common problem with many test suites is that they can take a long time to
run. The longer they run, the less likely you are to run the tests. This
module borrows a trick from Apache::Registry to load up your tests at once,
create a separate package for each test and wraps each package in a method
named run_the_tests. This allows us to load perl only once and related
modules only once. If you have modules which are expensive to load, this can
dramatically speed up a test suite.
