如何运行arquillian-jms-mdb？新手遇容器启动但测试未执行问题

Hey there, let's figure out why your Arquillian MDB tests aren't executing even though your JBoss 7.2.0 container starts up successfully. I’ve tackled similar quirks with Arquillian and JBoss before, so here’s a step-by-step breakdown to diagnose the problem:

1. Double-Check Your Arquillian Configuration #

First, take a look at your arquillian.xml file (usually in src/test/resources):

• Ensure you’ve specified the correct jbossHome path for your JBoss 7.2.0 installation. A wrong path can lead to partial container startup or deployment failures that aren’t immediately obvious.
• Verify the container mode: If you’re using managed mode (the default for most setups), confirm there are no typos in the container adapter configuration (e.g., org.jboss.arquillian.container:arquillian-jboss-as-managed-7).

2. Validate Maven Dependencies & Plugin Setup #

Your pom.xml is critical here—misaligned versions or missing plugins can prevent tests from running:

• Arquillian & JBoss Adapter Versions: Make sure the Arquillian JMS extension and JBoss container adapter versions are compatible with JBoss 7.2.0. For JBoss AS 7.x, you’ll want adapters specifically built for that version range (avoid using WildFly-only adapters here).
• Test Plugin Configuration: Arquillian integration tests typically use the maven-failsafe-plugin (not surefire, which is for unit tests). Check that the plugin is bound to the integration-test phase and configured to scan for test classes with a suffix like *IT.java (the standard for integration tests). Example snippet to verify:

  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-failsafe-plugin</artifactId>
    <version>3.0.0-M7</version>
    <executions>
      <execution>
        <goals>
          <goal>integration-test</goal>
          <goal>verify</goal>
        </goals>
      </execution>
    </executions>
  </plugin>
  

3. Dig Into Logs for Clues #

Enable verbose logging to uncover hidden issues:

• Run Maven with debug mode: mvn clean install -X. This will show you detailed logs about how Arquillian is setting up the container, deploying the test archive, and scanning for tests. Look for lines indicating deployment failures, missing test classes, or container connection issues.
• Check JBoss’s server logs (located in standalone/log/server.log). Look for errors related to JMS queue creation, MDB deployment, or missing dependencies—these could prevent the test from even being detected.

4. Verify Test Class Annotations #

Make sure your test class is properly annotated for Arquillian:

• The test class must have @RunWith(Arquillian.class) to trigger Arquillian’s test lifecycle.
• You need a @Deployment method that builds a test archive containing your MDB class, any required JMS configuration files (like ejb-jar.xml or jboss-ejb3.xml), and dependencies. If the archive is missing critical components, the test won’t execute.
• Confirm your @MessageDriven annotation on the MDB is correctly configured to match the JMS destination (queue/topic) defined in JBoss.

5. Test Deployment Manually #

To rule out container or archive issues:

• Locate the test archive generated by Maven (usually in target/ with a name like *-test.jar or *-test.war).
• Manually deploy this archive to your running JBoss 7.2.0 instance. If deployment fails, the issue is with your archive or MDB configuration—not Arquillian’s test execution.

内容的提问来源于stack exchange，提问作者user2902165