[Jboss-dev-forums] [Design of JBoss Build System] - Re: test target

[<tom...@jb...>]

anonymous wrote : Yes, that's certainly a limitation. Is this an actual need at this point? If so, we could change that attribute to be an Ant patternset refid instead of the actual pattern. 

I really only need this to segment out the performance tests, which use the same XXXTestCase naming convention and is under the same org.jboss.test.remoting root package as the rest of the other functional remoting tests.  This is because I don't always want to run the performance tests when running functional tests, as they takes a long time.  

I would not be opposed to just changing the package structure to be something like org.jboss.test.remoting.functional and org.jboss.test.remoting.performance so I can segment out the different tests.  The only problem I see with this, is there is no way that I know of to create another source element for this (because both would live under src/tests/ directory, both would have to be named 'tests').  I could create a src/performance/ directory and put the tests there, but this does not seem appropriate.


anonymous wrote : The pathElements tag is a special tag which resolves to the inputs of your source - and the jars in the Classpath of your inputs manfest. So if you have: 
 
Using the show target for the runtests.test, didn't work for me:

C:\Projects\JBoss\JBossRemoting\remoting>ant -f jbossbuild.xml show -Dshow=runtests.test
  | Buildfile: jbossbuild.xml
  | 
  | BUILD FAILED
  | Target `show' does not exist in this project.
  | 
  | Total time: 0 seconds
  | C:\Projects\JBoss\JBossRemoting\remoting>ant -f release.xml show -Dshow=runtests.test
  | Buildfile: release.xml
  | 
  | show:
  | 
  | BUILD SUCCESSFUL
  | Total time: 0 seconds

However, using ant -v shows that '..\remoting\output\classes\main' (which I would expect due to having ) and '..\remoting\output\classes\tests' is include in the JUnit classpath when running the tests.  So trying to exclude certain test jars won't matter anyways.  Am not sure how to find a solution to my particular problem of scoping the classes I want to include in test runs, but maybe a solution to the previous problem (performance vs functional tests) will present a solution to this as well.


anonymous wrote : I've never liked the idea of passing arguments to tests this way. 
  
So given that my test example may not be a good example of why jvmarg is needed, I have another, more valid one.  I have been working on SSL transport for remoting.  This means that I'll need to be able to declare where the key store is located via a system property (i.e. -Djavax.net.ssl.keyStore=.keystore).  This one is outside my control :)



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875842#3875842

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875842