Great post!
So the first thing is you can compile all your templates as part of a
CI build as they are statically typed (for ssp, jade, scaml); so you
can catch templates breaking due to model/controller/API change -
which tends to be the most common cause of stuff breaking
http://scalate.fusesource.org/documentation/user-guide.html#precompiling_templates
In terms of integration testing; you may want to do that inside your
container (e.g. web connector/container + MVC layer or framework of
your choice + scalate).
We have a little integration test framework we tend to use to test
using scalate inside Jetty...
https://github.com/scalate/scalate/blob/master/samples/scalate-sample/src/test/scala/org/fusesource/scalate/sample/SampleTest.scala
scaladoc here:
http://scalate.fusesource.org/maven/1.5.2/scalate-test/scaladocs/index.html
e.g. here's the assertions...
http://scalate.fusesource.org/maven/1.5.2/scalate-test/scaladocs/org/fusesource/scalate/test/WebDriverMixin.html
Or you could try things like Selenium/WebDriver for something a little
more webbyish (which can test different web browsers too)
--
James
-------
FuseSource
Email: ja...@fusesource.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/
Open Source Integration and Messaging