The JBoss Testsuite module is a collection of JUnit tests which require a running JBoss instance for in-container testing.  Unit tests not requiring the container reside in the module they are testing.

The setup and initialization of the container is performed in the testsuite's build.xml file.  The testsuite module also provides utility classes which support the deployment of test artifacts to the container.

• HowToRunTheTestsuite - Running the JBoss Testsuite

• HowToRunTheTestsuiteAgainstJBossEAP - Running the testsuite against the secured JBoss EAP distribution

• HowToExecuteMatrixTests - How to test Jboss against older client versions

• TestsuiteChanges - Changes to the testsuite and how to use it (assumes familiarity with existing testsuite).

• FunctionalTests - Tests which don't run against a server instance.  Where to put them and how they are integrated into the testsuite.

• HowToWriteAUnitTest - How to add a test to the JBoss Testsuite.

• TestsRequiringCustomConfiguration - What to do when you need to add a test requiring a custom configuration of JBoss.

• TestsRequiringDeployedArtifacts - How to write a test which depends upon a deployed artifact such as an EAR.

• JUnitsForDifferentConfigurations - How to keep JUnit results after running the same test against different configurations.

• ServerControllerTasks - How to control JBoss instances from Ant in a reliable way.

• TestsuiteTroubleShooting - What do when the testsuite doesn't work right.

• TestCaseTargetAndServerMapping - Maps test suite class names to their targets and server configurations

• FlakyTestResolution - A page dedicated to identifying and resolving 'flaky' tests.