One error that is often made is that less time is spend making tests well organized, look good, documented, etc .. than time spend on the code that is tested as if tests were second order code citizens (I believe the opposite is true)
This module comes with an example that shows you how to force your tests to have a description.
While this is great, I hoped for more examples. I would also prefer to see this under Perl::Critics::Test and the different tests to be policies.
I like where this is going.
4 out of 4 found this review helpful. Was this review helpful to you? Yes No