Enterprise Java Development@TOPIC@

Chapter 93. IT Testing with IDE

93.1. Run IT Tests Against Server
93.2. Debug Code Running on Server
93.3. Summary

93.1. Run IT Tests Against Server

Figure 93.1. Deploy Artifacts

$mvn clean pre-integration-test

...

22:51:43,460 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named GreeterEJB in deployment unit subdeployment "ejb-basic-ejb.jar" of deployment "ejb-basic-ear-4.0.0-SNAPSHOT.ear" are as follows:

        java:global/ejb-basic-ear/ejb-basic-ejb/GreeterEJB!info.ejava.examples.ejb.basic.ejb.GreeterRemote
        java:app/ejb-basic-ejb/GreeterEJB!info.ejava.examples.ejb.basic.ejb.GreeterRemote
        java:module/GreeterEJB!info.ejava.examples.ejb.basic.ejb.GreeterRemote
        java:jboss/exported/ejb-basic-ear/ejb-basic-ejb/GreeterEJB!info.ejava.examples.ejb.basic.ejb.GreeterRemote
        java:global/ejb-basic-ear/ejb-basic-ejb/GreeterEJB
        java:app/ejb-basic-ejb/GreeterEJB
        java:module/GreeterEJB

22:51:43,563 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: ejb-basic-ear-4.0.0-SNAPSHOT.ear

  • Deploy artifacts using Maven command from either module parent or IT test module

  • Build from parent will re-build, deploy, and leave deployed the artifacts

Figure 93.2. Run IT Tests

Run IT Tests

  • Can select a specific test or package of tests

Figure 93.3. IT Test Results

IT Test Results

Make JUnit Tests IDE-friendly

Leverage reasonable hard-coded defaults and filtered resource files to make JUnit tests IDE friendly so that much of heavyweight Maven setup and teardown can be skipped when focusing on specific tests.

93.2. Debug Code Running on Server

Use Debug Start Server Option for Embedded

The following information is for remote debugging a standalone server. If you are using the IDE embedded mode, just re-start your server using the debug option and add source references as needed.

Figure 93.4. Enable Remote Debugging in Server

# wildfly-8.1.0.Final/bin/standalone.conf

# Sample JPDA settings for remote socket debugging
JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"

  • Not required when using embedded server (just use debug-as)

  • Standalone server must be restarted after making this edit

Figure 93.5. Configure New Debugger Client

Configure New Debugger Client

Figure 93.6. Standalone Server Debugger Listen Port

=========================================================================

Listening for transport dt_socket at address: 8787
22:51:31,542 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
22:51:32,276 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
22:51:32,526 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.1.0.Final "Kenny" starting

Figure 93.7. Connect Debugger to Remote Process

Connect Debugger to Remote Process

  • Debugger Client port must match what JBoss debugger listen port

Figure 93.8. Create Breakpoint in EJB Module

Create Breakpoint in EJB Module

  • You can optionally add modules now to resolve source code references

Figure 93.9. Run IT Test/Hit Breakpoint/No Source

Run IT Test/Hit Breakpoint/No Source

  • Execution will stop at server breakpoint

  • No sourcecode will show up if not yet in search path

Figure 93.10. Add Source

Add Source

  • Add as many projects as you wish

Note

You may have to stop and re-run your test for the source code path to take effect.

Figure 93.11. Connect Debugger

Connect Debugger

  • Notice we are seeing variables as well as line of execution

93.3. Summary