comment on

Sounds like a Big Can of Worms™ to me. I would simply enforce that all changes be committed to a CVS system so that in case a designer breaks the interface you can roll back. Also, you have two webservers ... one in-house development server and a live production server. All changes are made to the devel server and nothing is rolled out until it has been tested and is correct.

Also, i think that writing test cases of expected HTML output is a waste of time as well.* Hell, is it even practical? I mean, i envision a case where a designer needs to reposition the data. Are you going to require that (s)he get a back-end coder to change the test suite just so the template will check out? Better to test that data is correct and let the designer put it where ever they need. And if they screw up, you simply back out an older revision from CVS.

CVS and a seperate development server are what we use here at work. Sure, a test suite that ensures modifications won't break would be nice, but the time it takes to develop and keep it up to date surely is not worth the time you will have to invest.

jeffa

* unless i'm writing tests for DBIx::XHTML_Table ...

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re: Testing Template, or should I write a diff for TT templates? by jeffa
in thread Testing Template, or should I write a diff for TT templates? by EvdB

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks