I agree with dragonchild that this is very domain specific.
Moreover, I wonder whether there's really a sufficiently general test-module here given all the combinations. In most cases, I suspect that a short user function at the top of the test file or in a fixture file would be clear and avoid adding an extra dependency.
Alternatively, instead of writing a new module, how about adding these as options to Test::Differences? Or perhaps adding a generalized callback to filter input before making the comparison?
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: Whitespace issues in testing
by xdg
in thread Whitespace issues in testing
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |