His earlier article on testing was pretty good too: "Grouping everything under functions also has the benefit of reminding other developers that it's okay to write more functions. For example, if every test for every action in a controller ought to verify access permissions, it's easy to write a helper function to set up an environment with and without access permissions to test both ways. (Some of these test functions get promoted to project-specific test libraries.)"
http://www.modernperlbooks.com/mt/2013/05/organizing-perl-test-files.html On Mon, Jul 22, 2013 at 9:24 AM, G. Wade Johnson <[email protected]> wrote: > chromatic nails some of the subtly of writing good tests here. > > http://www.modernperlbooks.com/mt/2013/07/good-tests-hate-ambiguity.html > > He doesn't provide any advice you can directly use, it's more of a "how > do I think about this thing" kind of post. > > G. Wade > -- > The function of good software is to make the complex appear to be > simple. -- Grady Booch > _______________________________________________ > Houston mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/houston > Website: http://houston.pm.org/ > -- 2048D/E67424BF (GnuPG) <http://freemonad.org/csb/files/gpg>
_______________________________________________ Houston mailing list [email protected] http://mail.pm.org/mailman/listinfo/houston Website: http://houston.pm.org/
