"... able to write a class definition into some file and run a script that would automatically generate the Moose class and the tests for me ..."
How would you tell the definition what methods to call and how would you pass the necessary arguments to them? How would this process know what values to expect?
Just write the tests and be done with it. Don't worry about DRY with unit tests. The more repetitive and explicit the better. Leave clever out of your unit tests -- try to avoid loops as much as possible. Each test should be able to comment out with a simple # -- loops make you code in exceptions. Unit tests should be KISS - keep it simple and stupid. Study the unit tests in your favorite CPAN distributions: some are great and some are not so good and some are downright embarrassing.
Make your unit tests double as working examples of your code. Simple tests. Simple one line examples.
In reply to Re: Automation of testing of Moose class structure
by Anonymous Monk
in thread Automation of testing of Moose class structure
by nysus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |