They are an improvement, though the extent of that will vary from user to user. For example, it is much easier to say:
./cluster/build.sh tests Than to figure out the test class names and then look up the proper target to call and the properties to set (in case you forgot, like I always do). It basically makes it easier to run smaller chunks of the tests. If you still just want to run one single test, then there is no real advantage. It is possible that there could be new dependency related issues, but I hope to resolve the with new build system components which can figure these out automatically... well with minimal configuration is more likely. --jason > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED]] On Behalf Of Scott M Stark > Sent: Thursday, September 19, 2002 2:36 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Build System... any ideas > > > I don't really see how module local tests are any improvement over the > test and > one-test targets in the existing testsuite module. In some ways it is a > problem > because now you have additional dependencies to build and run the tests in > the module. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, September 18, 2002 10:29 PM > Subject: RE: [JBoss-dev] Build System... any ideas > > > > David and I talked about this on the way back from Tahoe. I would like > > to revisit the entire TestSuite, putting a testsuite in each module, > > which would perform Unit tests for components and parts of components > > for that module alone. Then the jboss/testsuite would be an integration > > testsuite. > > > > This way, if you are working on bits from the cluster module, you can > > write simple tests to validate your component and run the tests quickly. > > Then when you are satisfied, you can write an integration test, which > > would actual test a real component inside of a JBoss instance. > > > > This will get us more coverage, but will also encourage developers to > > make smaller, simpler tests for stuff and make it more likely they will > > run them, as it won't take forever. > > > > Also, on the subject of build systems and testsuites, I have been toying > > with the idea of allow Java and Jython tests to be run together. Using > > Jython it will be faster to throw together small and functional tests > > with much less code and a lot less trouble. We would still need Java > > tests to run stuff that is type dependant, but the two could live > > together happy. > > > > The build system overhaul is a dependency of this I believe. > > > > I have been planning on doing all of the above... just I haven't had the > > time to make any progress. Also I really want to finish the basic > > command line console framework. > > > > Fuck, I need my boss to stop making me work on their lame ass projects. > > Who cares about that shit really... bah! > > > > --jason > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
