Re: How do you structure and run module test code?

I use Devel::Cover to make sure I have tests for all my features. This usually means adding checks to existing test files, as opposed to creating new test files.

Regarding the naming of test files, just use names that are meaningful. I always like to have an extremely simple test which does only one thing related to my code (as opposed to the generic pod/load/critic tests). I usually name it basic.t. This makes things easier to debug when things go horribly wrong.

After release, if someone submits a bug report, I normally create a dedicated test file that sensitizes that bug.

Comment on Re: How do you structure and run module test code? Download Code

Replies are listed 'Best First'.
Re^2: How do you structure and run module test code? by hippo (Archbishop) on Feb 23, 2017 at 14:24 UTC
That's an excellent point about the bug reports. (++) I try to follow this procedure when a bug report is raised: 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. Iteratively: attempt a fix and run the test file until all tests pass. Release the new version. 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.	[reply]

Replies are listed 'Best First'.

Re^2: How do you structure and run module test code?
by hippo (Archbishop) on Feb 23, 2017 at 14:24 UTC

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

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

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.
Iteratively: attempt a fix and run the test file until all tests pass.
Release the new version.
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.

[reply]