From: <rya...@jb...> - 2005-04-29 00:06:51
|
"tom...@jb..." wrote : 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'). For performance tests, you could add a seperate target which calls Junit directly. It would need JBBUILD-71 implemented to be able reference the classspath and other things you'll need. It is something we need in general, but will help with this particular case. anonymous wrote : Using the show target for the runtests.test, didn't work for me: Sorry, that should have been ant -f jbossbuild.xml show -Dshow=runtest.tests | | | | It is based on the ID of your source. target.id | | | | anonymous wrote : 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. | | | | Honestly, all of this is making me wonder how much work we should put into making testing a core part of jbossbuild. I've already raised 2 JIRA issues for you to be able to run your tests, so this tells me we may need to rethink how we define tests for a project. I know aop has an extensive testsuite which seems like it would accept no generic solution. | | | | Perhaps projects should define their own test targets, at least until we get the build part of jbossbuild complete. | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875850#3875850 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875850 |