in reply to Re: How do you structure and run module test code?
in thread How do you structure and run module test code?

That's an excellent point about the bug reports. (++)

I try to follow this procedure when a bug report is raised:

  1. Write a new test file to reproduce the bug (ie. the test(s) fail on the unpatched code). The test file is named after the report number.
  2. Iteratively: attempt a fix and run the test file until all tests pass.
  3. Release the new version.
  4. Keep the test file in the suite to prevent regression because there is nothing more annoying than having to patch the same bug twice.

Where possible I try to provide such a test file when reporting bugs in other people's code as it makes less work for them and (hopefully) illustrates precisely what the bug is.

  • Comment on Re^2: How do you structure and run module test code?

In Section Seekers of Perl Wisdom