DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33980>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33980 ------- Additional Comments From [EMAIL PROTECTED] 2005-03-14 06:52 ------- Yes, definitely use JUnit. Thanks for volunteering to do this extra work. I would suggest waiting, however, until someone else does agree this code should be included in beanutils, otherwise your time may be wasted. The question is not really whether your code *works*, but whether the problem it solves is sufficiently common to make it part of the standard library; I think so but others may not agree. Here's how to write/execute unit tests for beanutils: 1. install Maven (maven.apache.org) 2. install subversion client 3. Use subversion to check out the existing commons-beanutils project (http://svn.apache.org/repos/asf/jakarta/commons/proper/beanutils/trunk). 4. Use subversion to check out the commons-build project as a sibling directory to the one you checked commons-beanutils out into. (http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk). 5. from the beanutils root directory, run "maven test" to execute the existing unit tests. This command will automatically download any libraries needed to run beanutils and the unit tests, so the first time this is run it may take some time and network bandwidth. Now you can add your new tests to the existing tests in directory src/test/org/apache/commons/beanutils/... There are plenty of tests in there already that you can base your new tests on. When you run "maven test", information about failed tests will go into directory target/test-reports. Note that at the moment the "MemoryTestCase" test is failing; this is a known issue that is being worked on. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
