Okay, no worries. What don't you get? Which tests specifically are you thinking of when you say then "involve several functional modules"? Just one for an example, so I can see where you are coming from is fine.
Basically most of jboss/testsuite will remain the same, as many of those tests require a running JBoss instance and use many components from many modules to function. But there are a subset, like the proxy compiler tests, or the JBossMQ selector parser tests, which do not. So far most of our tests have been functional tests of a component from start to end. I am suggesting that we could make more tests which test individual parts (with out running a JBoss instance)... perhaps using mock objects for bits that we need to run them. This will give us more coverage and will allow the functional tests to simply test the integration & not the functionality of the individual components. By putting these independent tests in the corresponding module, we make the testsuite more maintainable by preventing jboss/testsuite from becoming insanely huge. Does that make sense or shall I explain more. Perhaps I am not wording things correctly, or I am taking some bit of knowledge for granted? --jason > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:jboss- > [EMAIL PROTECTED]] On Behalf Of Scott M Stark > Sent: Thursday, September 19, 2002 4:32 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Build System... any ideas > > I still don't buy it. Many of the existing tests involve several > functional modules > so how do I associate the test with its module? The compilation issue is a > simple > by product of having a huge monolithic build file, and further complicated > by > xdoclet having to be run as a first pass to generate the code. I better > not wake > up one morning and have the testsuite laying in pieces in CVS without a > clear > consensus on this approach. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > > ----- Original Message ----- > From: "David Jencks" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 19, 2002 4:15 PM > Subject: Re: [JBoss-dev] Build System... any ideas > > > > On 2002.09.19 18:05:46 -0400 Scott M Stark wrote: > > > Add -Dnojars=true during the run of the single test and zero > compilation > > > time is the result. > > > > Umm, yes, I know about nojars, I wrote it. > > > > It doesn't help much if you changed the test and need to recompile, the > > situation I find time consuming. > > > > > Add -Djbosstest.nodeploy=true and you can also avoid having to deploy > the > > > tests > > > into the server. > > > > Doesn't this require you to copy the appropriate test jar into the > deploy > > directory? Are there any deployments that take a significant amount of > > time? > > > > I routinely run single tests in 10 seconds with these > > > options. Refactoring > > > the entire testsuite for a simple usage problems is silly. > > > > Having to spend 7 minutes to try a simple change to a test is a lot > > sillier. > > > > > > > > > > Breaking up the huge monolithic build file into seperates test files > > > would be a good thing. > > > This is what we had in 2.4 and it was nice when we had < 200 tests. > Now > > > as we > > > approach 1000 its time to revisit this as well. > > > > Agreed, this is a better solution, but also more work. I think the > > test/module in the modules is the way to go here. > > > > david jencks > > > > ------------------------------------------------------- > 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
