EJB3 Patch Testing instructions for JBossAS 4.0.5.GA

Run JBoss AS Testsuite

1. Download JBossAS 4.0.5.GA source from Subversion and build using JDK1.5 (JBossAS 4.0.5.GA when built with jdk1.4 does not build ejb3)

2. build/output/ folder should contain two distributions. jboss-4.0.5.GA and jboss-4.0.5.GA-ejb3

3. Remove jboss-4.0.5.GA from build/output and make a copy of jboss-4.0.5.GA-ejb3 as jboss-4.0.5.GA. (This is done because the AS testsuite by default runs against jboss-4.0.5.GA distribution which does not have ejb3. Other option is to run the AS testsuite by specifying the jboss.dist property to jboss-4.0.5.GA-ejb3)

4. Before running the testsuite replace the patched jars attached to the JIRA in the output distributions.

5. Make a copy of the original output to check if any failures are actual regressions introduced by the patch. i.e you can run the test without the patch to see if it a regression.

Run EJB3 Testsuite.

1. The ejb3 testsuite runs against the jboss-4.0.5.GA-ejb3 distribution.

2. Build JBossAS.

   build/build.sh

   and patch output. (You would have already done this while running the AS testsuite).

3. Copy the ejb3 directory to another name

   mv ejb3 ejb3.orig

    

4. Checkout ejb3 branch that contains the patch from SVN. 

   svn co https://svn.jboss.org/repos/jbossas/branches/BRANCH_NAME/ejb3

     This step might not be necessary, but skipping it could cause the testsuite to fail and/or additional tests from the new branch to not be run.

5. Build ejb3. 

   ant -f ejb3/build.xml

    

6. Patch the jars under ejb3/output/.

7. Build ejb3 tests.

   ant -Dnode0=localhost -Dnode1=$MYTESTIP_1 -DudpGroup=xxx.xxx.xxx.xxx  -f ejb3/build-test.xml

     You should use localhost as node0 otherwise some hardcoded tests will fail.  These tests have been fixed in some branches, but not others.  node1 should be set to all the clustered tests to pass.  "udpGroup" is optional, but prevents other jboss instances on the network from interfering with the testsuite.

8. Run ejb3 tests.

   ant -Dnode0=localhost -Dnode1=$MYTESTIP_1 -DudpGroup=xxx.xxx.xxx.xxx ejb3/build-test.xml tests

    

9. Make sure you have a copy of the original output to check for regressions.

NOTE: The ejb3 testsuite was never 100% for jboss-4.0.5.GA. The following tests are expected to fail.

• Suite:       org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase

Test:        testQuerySingleResultExceptions

Type:        error

Exception:   javax.ejb.EJBException

Message:     javax.persistence.NoResultException: No entity found for query

• Suite:       org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase

Test:      

testQuerySetHintAndParameter

Type:        error

Exception:   javax.ejb.EJBException

Message:     java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!

• Suite:       org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase

Test:        testRuntimeException

Type:        failure

Exception:   junit.framework.AssertionFailedError

Message:     expected:1 but was:0

• Suite:       org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase

Test:        testRollback

Type:        failure

Exception:   junit.framework.AssertionFailedError

Message:

• Suite:       org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase

Test:        testSSLBindings

Type:        error

Exception:   javax.naming.NamingException

Message:     Could not dereference object

EJB3 Patch Testing instructions for JBossAS 4.2.0.GA

1. With JBoss AS 4.2.0.GA there are no separate distributions for ejb3. The output will have a jboss-4.2.0.GA distribution which has to be patched and tested.

2. Follow the instructions as above, except omit Step 3. in running JBoss AS section.