P6Spy Integration Testing
If you're looking for the configuration with the particular app server, check the official docs: [Installation] (http://p6spy.github.io/p6spy/2.0/install.html)
git clone https://github.com/p6spy/p6spy-it.git
cd p6spy-it
export ORG_GRADLE_PROJECT_container=<app_server>; ./gradlew clean unitTest
where following are available <app_server>s provided:
wildfly81x- Wildfly 8.1.0.Finaljboss61x- JBoss 6.1.0.Finaljboss51x- JBoss 5.1.0.GAjboss42x- JBoss 4.2.3.GApayara4x- Payara 4.1.144glassfish4x- Glassfish 4.0glassfish31x- Glassfish 3.1.2.2tomcat9x- Tomcat 9.0.41tomcat8x- Tomcat 8.5.61tomcat7x- Tomcat 7.0.107tomcat6x- Tomcat 6.0.53tomee7xweb- Tomee 7.1.2 Webprofiletomee7xplus- Tomee 7.1.2 Plustomee7xplume- Tomee 7.1.2 Plumetomee8xweb- Tomee 8.0.4 Webprofiletomee8xplus- Tomee 8.0.4 Plustomee8xplume- Tomee 8.0.4 Plumetomee8xmicro- Tomee 8.0.4 Microprofilewls12x- WebLogic 12.1.3 (for development)wlp16x- Websphere Liberty Profile 16.0.0.2
However, due to travis-ci restriction on jdk availabiluty (jdk 7 not working), only following run in our CI env:
wildfly81xpayara4xglassfish4xtomcat9xtomcat8xtomcat7xtomcat6xtomee7xwebtomee7xplustomee7xplumetomee8xwebtomee8xplustomee8xplumetomee8xmicrowls12xwlp16x
To debug JUnit test (not in-container part) run, use:
export ORG_GRADLE_PROJECT_container=<app_server>; ./gradlew clean unitTest -Dtest.debug=true
and connect via the IDE of your choice for remote debugging afterwards using the port 5005.
To debug JUnit test (in-container part) run adopt arquilian.xml respectively afterwards use:
export ORG_GRADLE_PROJECT_container=<app_server>; ./gradlew clean unitTest
and connect via the IDE of your choice for remote debugging afterwards using the port specified.
Idea is to setup container tests in a way that we can have full control on what's happening and the configuration steps should be documented per container in official docs: [Installation] (http://p6spy.github.io/p6spy/2.0/install.html)