Want more powerful to-do lists? Want to manage your work/personal projects online? Then check out Basecamp — it's where Ta-da came from.

Perl Test::Class backlog

bullet $object->SKIP_ALL should just skip tests in current object
bullet Write some cookbook POD
bullet Look at David's patch to load Test::Classes on request
bullet Clarify why/where the xUnit style is useful in the docs
bullet See if we can steal anything neat from NUnit and Ruby's Test::Unit
bullet Annotate test description with the method name ?
bullet Clean up documentation for running multiple classes
bullet Consider using Test::Tester instead of Test::Builder::Tester
bullet Comment on http://martinfowler.com/bliki/JunitNewInstance.html
bullet See if there is anything new to steal in recent JUnit releases
bullet Think about ways to support multiple fixtures in a single class.
bullet Use the class variable style of test class in docs?
bullet Vary the order of test methods / classes easily
bullet Separate out Test::Class::Tutorial
bullet Check whether we can reduce the prerequisites
bullet Refactor test suite
bullet See whether the bizarre L<> syntax is still needed in POD
bullet Refactor runtests... lord is it ugly
bullet Mail out about the 1.0 release to perl-qa, tdd, agile-testing, etc.
bullet Look at using pperl/Module::Refresh and T::C together for faster startup times
bullet Should SKIP_CLASS should skip all the tests or just one
bullet Look at rationalising the object/class behaviour
bullet Have another go on getting it on module list
bullet Add link to annocpan.org
bullet Make sure exit code logic matches that in the latest Test::Builder
bullet Have a ponder about how Test::Class and Test::Base might interact
bullet Consider renaming startup/teardown before/after like JUnit4
bullet Use JUnit 4.0's inheritance model for before/after running order?
bullet Have option to automatically add runtests to classes
bullet See what we can steal from TestNG
bullet You can't run classes just consisting of setup/teardown methods with tests coz it thinks there are no tests. Bug? Feature?
bullet ability to time test methods so we can run them in fastest-test order
bullet add ability to tag methods
bullet add ability to tag all methods in a class
bullet add more flexible approach to setting fixtures for a class
bullet look at integrating with role/trait modules
bullet Look at other things on CPAN that look "xUnit" ish
bullet Decent warnings for Test::Load if it encounters filenames that it doesn't understand
bullet Look at parametarised fixtures
bullet When we have a default test description from the test method we should probably annotate it with the name of the setup/teardown methods involved too.
bullet Also need to give startup/shutdown methods with default test description
bullet Look at fixing the asymmetric treatment of runtests() and expected_tests()
bullet See what we can steal from xunit.net
bullet Comment on the ordering of class execution for Test::Class->runtests
bullet Allow people to (optionally) skip inherited tests for people with long test runs.
check add links to modules / distributions that use T::C
check implement SKIP_CLASS
check Move the rest of my to do list for T::C here
check Warn if subclasses override public methods with :Test methods
check add link to this backlog to POD
check Allow individual test methods to be run
check Have a :Tests attribute that defaults to no_plan
check Consider having :Test munge multiple tests in a method to a single ok / not ok
check Allow user to interrogate the success / failure of test classes / methods (decided not to do this. Should probably be in the Test::Harness)
check Choose things from list below for 0.09 release
check T::C wiki (don't need one now perl-qa wiki is back)
check T::C mailing list (decided to use CPAN::Forum / perlmonks / perl-qa)
check Add to do items from the subversion repository
check Look at how the Aspect modules use T::C
check Add perlmonks questions on T::C to list
check Release 0.08
check Look at code coverage
check Consider moving to the POD section standard from Damian's Perl Best Practices
check Release 0.09
check Choose items from below for 0.10 release
check Check whether Test::Unit is still under development, and comment if it isn't
check Look at 0.08 test failures reported by cpantesters
check Release 0.10
check Choose items from below for 0.11 release
check Get links to modules in SEE ALSO to work on search.cpan.org
check Really fix the _test_classes bug
check Release 0.11
check Choose items from below for 0.12 release
check add link to CPAN::Forum
check Decide which features need to be looked at for a 1.0 release
check Release 1.0
check Look at using T::C with pperl & Test::Harness
check Add T::C ego links to del.icio.us
check Add link to perl-qa to POD
check Fix SKIP_CLASS problem David reported
check fix https://rt.cpan.org/Ticket/Display.html?id=11512
check Add link to extremeperl
check Release 0.12
check Add delicious T::C links to SEE ALSO
check add link to TPJ article on Test::Class
check Test::Prereq
check Change test name to test description to conform with TAP
check Move stuff from build_requires to requires so it works with CPANPLUS
check We're using UNIVERSAL::isa a few places where we shouldn't - fix it
check Add link to PTDN book's T::C chapter
check Add diag to failing tests that shows the object / class / method that failed
check Have a ponder about the TEST_METHOD regex idea Ovid suggested
check Add link to Advanced Perl, 2nd edition Testing chapter
check Make it work wiith latest T::B / T::B::T
check allow single test methods to be run
check Add Ovid's Test::Class::Load
check Dig out the todo tasks from the WIP/Personal mail
check Resolve rest of outstanding RT bugs
check Check Anno CPAN for feedback
check Check CPAN Forum for feedback
check Add references to Test::Object and Test::Group

Subscribe via RSS

Be notified of changes to this list via RSS: Rss

alt

Want to make your own to-do lists?

Ta-da List is a simple tool that lets you create to-do lists for yourself and for others. Sign-up today — it's fast and free.