-
1. Re: Integrate module tests into jbossas testsuite
rrajesh Mar 13, 2006 5:18 PM (in response to starksm64)The process to get the module tests as part of the overall testsuite, say, for the aspects module in jboss-head would be.
1. Create a "tests-aspects" target which does the following:
Build the test classes in the aspects module.
Start the required server configuration.
Run the tests.
2. Modify the "tests-report" target to include the xml test reports from /aspects/output/reports folder.
Both ejb3 and webservice modules could follow a similar procedure. -
2. Re: Integrate module tests into jbossas testsuite
ryan.campbell Mar 28, 2006 7:58 PM (in response to starksm64)Ok, the tests-aspects has been integrated into jboss-head, but not jboss-4.0, so this needs to be done.
We also need to do this for ejb3/webservice builds as well. I don't think the webservice tests are in 4.0, just head.
Rajesh, can you create JIRA tasks for the 3 items above? -
3. Re: Integrate module tests into jbossas testsuite
rrajesh Mar 29, 2006 4:06 PM (in response to starksm64)I have created JIRA tasks for the following:
Integrate aspects tests with jboss-4.0 testsuite
http://jira.jboss.com/jira/browse/JBQA-337
Integrate ejb3 tests with jboss-4.0 and jboss-head testsuite
http://jira.jboss.com/jira/browse/JBQA-338
Integrate webservice tests with jboss-head testsuite
http://jira.jboss.com/jira/browse/JBQA-339 -
4. Re: Integrate module tests into jbossas testsuite
rrajesh Mar 29, 2006 8:23 PM (in response to starksm64)The aspects module tests in Branch_4_0 (build-test.xml) lacks a single "tests" target which runs all the tests. This is present in the HEAD branch.
<property name="junit.junit.root" value="${project.thirdparty}/junit-junit"/>
in tools/etc/buildmagic/libraries.ent refers to a non-existant path. This causes the aspects tests build to fail in Branch_4_0 -
5. Re: Integrate module tests into jbossas testsuite
starksm64 Mar 29, 2006 8:52 PM (in response to starksm64)Nothing should be using the ../tools/etc/buildmagic/libraries.ent import any longer. Everything needs to be using the ../thirdparty/libraries.ent file.