Basically, testing your templates and your application shoud be two separate things.
You should use your app-testing-templates (core-templates)
to test your actual templates, ie designer-processed-templates (production-templates).
So, I envision somebody writing
Template::Test::Structure
( which comes with the commandline frontend tstest ),
which would make sure template-new is structurally equivalent to template-original,
warning the user of any differences, as in
tstest new original
new:34: variable FOO doesn't use FILTER `html' like original:44: in b
+lock "IF FOO"
new: missing variable BAR like original:66
This is all the template designer should be interested in (a structurally valid template),
unless, like
merlyn said, they also need to make sure the template is valid xml,
which they can go ahead and test by running the application test suite or whatever...
See also Unit Testing Generated HTML
MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" |
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). |
** The third rule of perl club is a statement of fact: pod is sexy. |