-
Notifications
You must be signed in to change notification settings - Fork 76
CTS Batch Test with WildFly
chengfang edited this page Oct 1, 2013
·
18 revisions
- The general guide for running tck7 (cts7) with WildFly: https://community.jboss.org/wiki/TCK7Guide
- Enable debug in $JBOSS_HOME/standalone.conf by uncommenting the following line and changing suspend to yes:
# Sample JPDA settings for remote socket debugging JAVA_OPTS="$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=y"
- start WildFly:
cd $JBOSS_HOME/bin ./standalone.sh
-
attach debugger to address 8787 in IDE
-
set breakpoints in cts test classes
-
run individual test that you want to debug, e.g.,:
cd /Users/cfang/dev/jboss-tck/tck7/trunk/src/com/ibm/jbatch/tck/tests/jslxml ant runclient -Dtest=testInvokeJobWithOnePartitionedStepExitStatus_from_web -Dtest.client=ParallExecutionTests.java
-Dtest.client sysprop tells cts harness in which test class to find the test method. The default value is Client.java. Since this test directory uses non-default test class names, so you need to specify -Dtest.client sysprop.
- to undeploy any test apps that may be left deployed on WildFly server after terminating the test run with Ctrl-C:
(in current test directory) ant undeploy