Johan Lindstrom

• About: I blog about Perl.

Recent Actions

• Commented on Discoverable tests and creating testing standards
  See also Devel::CoverX::Covered for another take on the problem of finding the way in a sprawling test suite. Devel::CoverX::Covered extracts and stores the relationship between covering test files and covered source files from a Devel::Cover cover_db. So you can jump...

Comment Threads

• mlawren.myopenid.com commented on Discoverable tests and creating testing standards

  It seems that the glob used by MakeMaker when running "make test" for finding tests is "t/*.t", which doesn't discover the tests in subdirectories. Does anyone know of a way of changing that?

• Michael G Schwern commented on Discoverable tests and creating testing standards

  I like the naming convention, I try to do that on my projects. Usually I go with one test file per method, especially in untested code methods to too much, so testing Foo::Bar->thing would be t/Foo/Bar/thing.t.

  I've tried the can_ok stubs before, it's why can_ok takes a list of methods, and I found it has major drawbacks. It gave the illusion of more test coverage than really existed (caveat, this was before Devel::Cover).

  For a dev team that isn't sold on the value of testing, it trained the developers to …

• Michael G Schwern commented on Discoverable tests and creating testing standards

  I add this to my WriteMakefile.

  test        => {
      TESTS => 't/*.t t/*/*.t t/*/*/*.t',
  },
  

• mlawren.myopenid.com commented on Discoverable tests and creating testing standards

  After a big search through the (unfortunately not well documented) Module::Install code I found the "tests_recursive" function that does the same thing to the required depth automatically.

• Ovid commented on Discoverable tests and creating testing standards

  Michael,

  Thanks for the thoughtful comments. I'll have to take that into consideration.