in reply to Using Test modules in production scripts

Listen to your feelings ;-). The tests in t/ should test your code and not do the work of the code itself.

Tests should be an independent instance that declares your code as correct, even after you changed parts of it or it is run on a different platform or your operating system is a new version. The important word is "independent". In your example you would write a test to check whether a missing directory produces an error message. If this test fails you know that that line doesn't work anymore in your script

Note it makes not much sense adding tests to old applications, unless you plan to rewrite, enhance or refactor the application, or adapt it to new environments

  • Comment on Re: Using Test modules in production scripts

Replies are listed 'Best First'.
Re^2: Using Test modules in production scripts
by xssnark (Initiate) on Feb 14, 2011 at 22:36 UTC
    Hello Jethro,

    Thanks so much for your input, this makes sense.

    In truth, it's not really an old application, however it is already complete and it works correctly.
    It's never been in production though, it isn't well tested :), and the development environment is not the same system as the production environment. So I figured late tests are better than no tests.

    TIR, X.