Its true that the main problem is xdoclet here. Its also the reason for a bug report about excessive memory usage during compilation. We need to have a comprehensive testsuite for the reason that Bill states, we cannot rely on a developer having to run individual module tests to validate system wide changes.
We also do need to address the monolithic nature of the testsuite. Having to run xdoclet and the compile to rerun a test is a waste of time. This does need to be broken down without losing the ability to run comprehensive testsuites. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Bill Burke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 14, 2003 9:23 AM Subject: RE: [JBoss-dev] The new "tests" target > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of David > > Jencks > > Sent: Friday, February 14, 2003 12:03 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-dev] The new "tests" target > > > > > > The testsuite is just not scalable, Bill, and is inappropriate for module > > level unit tests. Having the compile take 5-10 minutes for running just > > one test is ludicrous. > > > > If its not scalable, fix it. We need tests to run with the nightly build, > this is more important than saving you 5-10 minutes. When I make a global > change like InvocationResponse, I need to know that all tests are being > executed so that I don't fuck up everything. > > I turn off recompilation in testsuite/build.xml when I need to run a test > more than once quickly. Why does the stupid buildsystem rerun XDoclet > everytime you do a build? Why isn't there any dependency checking? This is > the real problem and why the build takes so fucking long. I miss the days > of the 2.x series when the buildsystem wasn't such a burden... > > > If you want to object, object to the change note when I announced this > > facility. > > > > I will see about getting all the module tests to run with the main > > testsuite and included in the report. > > > > This should have been done in the first place before it was encouraged to > put in modules tests.... > > > > > ricardo, all my tests just used stuff from build/tests or build/gen/tests > > (or whatever its named). I think we need an additional src/test-resource > > directory in each module for this purpose. We need a definition in > > buildfragments/defaults.ent and to include it in the > > _default:tests target. > > > > david jencks ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
