Showcase is a flexible format. A good approach would be to have a full set of Selenium tests for a tiles showcase. One of the showcase packages could also be a test suite, so we could have both in the same application. In Struts 1, the "taglib exercises" application is a test suite, it is also a good way to learn how the tag works, and we made it a module with other example applications. All test cases are examples and learning tools.
-Ted. On 11/23/06, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
David H. DeWolf ha scritto: > I actually agree, though there was discussion about making it a > "showcase". My preference would be to let the selenium test webapp be > our showcase. No reason to have 2 instances. > > Antonio? I don't know, my POV is that tiles-test could be used for all tests, even the simplest ones. For example, one day a user notices a strange effect on a tag and opens a JIRA issue, so we resolve it and put a Selenium test case. Adding this test case to the showcase would be unuseful for the user. I think that tiles-documentation (or tiles-showcase) will be a nice way to learn Tiles by examples, and it should not be tainted with test cases. Ciao Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- HTH, Ted. * http://www.husted.com/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
