I'm actually going to reiew items on the sf tracker to start fixing bugs for the next release (1.0 branch), and a big effort is required to write valid testcases before start writing fixes. Writing testcase doesn't require much "developer" knowledge of displaytag (you just need to know how to use it). So, is anybody there who have some time for help in this task?
writing a testcase means: - write a simple jsp which shows the bug (actually 2 -usually identical- jsps, one for the standard and one for the el version): you can find samples here: http://cvs.sourceforge.net/viewcvs.py/displaytag/displaytag2/src/test-resources/tld11/ -write a junit class which loads the jsp and make asserts on its content. You can find samples here: http://cvs.sourceforge.net/viewcvs.py/displaytag/displaytag2/src/test/org/displaytag/tags/ testcases can be committed directly to cvs (if you are a displaytag committer) or attached to the bug report (I will take care of committing them). Also valid testcases for existing but untested features are welcome (tests for pagination and sorting will be expecially useful as regression tests when performance-enhancement related changes will be committed) fabrizio ------------------------------------------------------- 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-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/displaytag-devel
