Author: manaRH Date: 2012-11-10 07:59:05 -0500 (Sat, 10 Nov 2012) New Revision: 15356 Modified: branches/enterprise/WFK-2_1/examples/readme.txt Log: bz 866924 readme.txt removals of not supported parts Modified: branches/enterprise/WFK-2_1/examples/readme.txt =================================================================== --- branches/enterprise/WFK-2_1/examples/readme.txt 2012-11-10 12:42:33 UTC (rev 15355) +++ branches/enterprise/WFK-2_1/examples/readme.txt 2012-11-10 12:59:05 UTC (rev 15356) @@ -66,26 +66,6 @@ mvn clean install -Darquillian=jbossas-remote-7 -Running integration test(s) in Eclipse --------------------------------------- -Right click on the project and select Properties. Select the Maven property sheet and in the first form field, -enter jbossas-remote-7 profile. -Click OK and accept the project changes. Before we execute tests, make sure that Eclipse has properly processed all -the resource files by running a full build on the project by selecting Clean from Project menu. -Now you are ready to execute tests. Right click on a test class and select Run As... > JUnit Test - -Detail guide is at http://docs.jboss.org/arquillian/reference/1.0.0.Alpha1/en-US/html_single... - - -Debugging of integration test(s) in Eclipse -------------------------------------------- -If you set a break point and execute the test in debug mode using a remote container, your break point won't be hit. -That's because when you debug an in-container test, you're actually debugging the container. -The test runner and the test are executing in different JVMs. Therefore, to setup debugging, - you must first attach the IDE debugger to the container, then execute the test in debug mode (i.e., debug as test). -That puts the debugger on both sides of the fence, so to speak, and allows the break point to be discovered. - - Running functional tests on an example =======================================