you can look at the existing test cases in the displaytag code, for example at: http://cvs.sourceforge.net/viewcvs.py/displaytag/displaytag2/src/test/org/displaytag/tags/ http://cvs.sourceforge.net/viewcvs.py/displaytag/displaytag2/src/test-resources/tld11/
There are both plain junit tests (mainly for utility classes and methods) and httpunit (servletunit) tests. There are also a few base classes which provide a simple framework for httpunit tests (setup servletunit, find and load jsp, run tests twice for the standard and el tld). All the tests are run during automated builds and you can always find the result here: http://displaytag.sourceforge.net/junit-report.html Producing a valid testcase, as well as run/integrate existing ones, to assure that nothing was broken, is the first prerequisite before thinking to commit changes to the code. Actually most of the patches uploaded on the tracker break something existing and at the same time they don't provide any way to automatically test new features. fabrizio On Sun, 19 Sep 2004 12:26:37 -0400, steven melzer <[EMAIL PROTECTED]> wrote: > can someone please give me examples of exactly what kind of test cases and > documentation they would like to see to get code considered for integration > with displaytag. are you looking for HTTPUnit type integration tests, or > simple JUnit black box tests? > > thanks, > steve ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ displaytag-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-user
