I have a few questions that I'd like to throw out to the JavaRanch community.
Any thoughts?
Simon
Originally posted by Simon Brown:
Hmmm ... no responses which is kind of what I was expecting. Most people that I've spoken to don't specifically test their tags.
Originally posted by ersin eser:
LoL...
Originally posted by ersin eser:
Simon, I am definitely going to follow your group and I would like to volunteer too. May be in documentation or tech review ;-) or basic coding :roll: Keep me in the loop.
Originally posted by Jessica Sant:
On a somewhat related note, if you'd like me to introduce you to Russ Gold, the lead guy on HttpUnit, he works here in my office...
Originally posted by Simon Brown:
How is that!
Simon
(I'm thinking that we could use HttpUnit to automate the TagUnit tests)
Originally posted by Michael Yuan:
Can you tell us more about how your new tagunit framework would be different? I looked up the web site but did not find much info ...
TagUnit is a framework whereby JSP custom tags can be tested inside the container, and in isolation to the pages on which they will ultimately be used. In essence, it's a tag library for testing tags within JSP pages. This means that it is easy to unit test tags, including the content that they generate and the side-effects that they have on the environment such as the introduction of scripting variables, page context attributes, cookies and so on.
In addition to "unit testing" tags, it is also useful to be able to test the cooperation between tags in a tag library, to ensure that the correct results are produced when tags are used in conjunction with one another. This is more like integration or component testing than unit testing, but is still important and possible within the same framework.
Finally, assertions can be made on the constraints specified within the tag library descriptor file, allowing tests to be made on the contract that a tag provides.
Originally posted by Simon Brown:
As you've probably seen from the tag testing examples from the XP book, you have to write the code that mimics the tag lifecycle. With the TagUnit framework, we're approaching this the other way and letting the container do this for us by testing tags within JSP pages. IMHO, it just makes testing tags easy - you don't have to write any Java code.