Its not clear to me. What is the module closest to testing the progation of the security context from a war to an EJB over SSL with authentication done using client certificates? I don't buy the organizational concept as most of the work is setting up the components, not the basic functionality testing. If there are truly module isolated functional tests, put these in the module, but cross module testing belongs in a teststuite module with the infrastructure setup to simplify creating, building and running the tests.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jason Dillon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 20, 2002 12:30 PM Subject: RE: [JBoss-dev] Build System... any ideas > So all of the examples you list which depend on other modules to > function are integration tests. You could imagine that for Naming you > might have a simple test which only tests the basic protocol > handshaking, versioning or whatever. For transactions you might have a > simple test to make sure that the UserTransaction class functions as > expected. I can't think of an example of security... 'cause don't > really know anything about it. > > My point is that most of our tests cover a vary large area. A single > test might hit deployment, ejb container startup, jndi proxy factory > lookup, factory creation, proxy invocation. > > I agree that these tests are very important and needed, but what about > testing each of these steps in isolation? This would help detect finer > grained problems faster and provide better coverage overall. > > That is one point, the second is where those tests should go. I believe > they should be closer to the code which they are testing, rather than > put into a monolithic testsuite module. BUT this is only for tests as I > mention above, which only test the components. One reason for this is > for modules which span projects, the core testsuite for the code will > move with it, rather than have to pick apart jboss/testsuite for the > correct bits. > > This is an organizational concept, where module test code stays with the > module, where tests which cover more than one module live in the > testsuite module. > > Take the jboss/common module. This module depends on nothing. There > are many classes here which could benefit from simple tests to validate > the functionality of the code which resides here. These classes are > also used through-out the entire server, so they will also be tested by > other tests as well. That does not mean that they are better suited to > live in the testsuite module. > > As it stands right now, the testsuite module is too big and too complex. > By moving the non-dependent tests closer to the code they are testing we > simplify and organize. I believe that a simple and organized testing > system will help encourage developers (new and old) to write more tests. > > > It seems clear to me... > > --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
