Swishetest Wishlist

From Swishewiki

• test passing bad data to the API. How does it handle it?

• follow guidelines in QA.perl.org's Testing Guidelines

• read Andy Lester and MJD's slides

• What if you call the indexer incorrectly? Should it die? Coredump? Whatever the choice, document it and define it.

• Tests, docs and code must all agree with each other.

• What are your edge cases? What if you index zero documents? Only one?

• Are there speed concerns? Should you be verifying that a given process should take less than a certain amount of time? Test::Benchmark will help you here.

• Add t/pod.t and t/pod-coverage.t for accuracy. See WWW::Mechanize for examples to steal. You can take them directly without changes.

• Since you're exporting functions, make sure they're getting exported correctly.

• Use Devel::Cover to make sure you're covering all the options you can be.

• Allow for executables not in /usr/local/bin

• Make sure that in the cases of warnings and death that your module is acting accordingly. See Test::Warn and Test::Exception for how.

DONE ITEMS:

• use portable not_rand() function instead of including a big data set in the distro (done)