Permalink
Browse files

explain how to export the archive for a single test

  • Loading branch information...
1 parent 30e3095 commit 45465b2b77bdb8a8e8ef7514f8b12b19681f6879 @mojavelinux committed May 11, 2012
Showing with 4 additions and 2 deletions.
  1. +4 −2 guides/getting_started_rinse_and_repeat.textile
View
6 guides/getting_started_rinse_and_repeat.textile
@@ -534,7 +534,7 @@ When you click the Debug button, JBoss AS should resume, then stop again when it
h3. Export the Deployment
-Sometimes you need to get a little bit more insight about what Arquillian is deploying to the server. Fortunately, Arquillian provides a way to export the archive just before deploying it to the server. This feature is controlled by a property in the engine configuration, which can be set in arquillian.xml. Simply specify an export location in the @deploymentExportPath@ property and Arquillian will export the archive to disk automatically.
+Sometimes you need to get a little more insight about what Arquillian is deploying to the server. Fortunately, Arquillian provides a way to export the archive just before deploying it. This feature is controlled by a property in the engine configuration, which can be set using arquillian.xml. Assign a relative or absolute export directory to the @deploymentExportPath@ property of the @<engine>@ element and Arquillian will export the archive to that location for any Arquillian test you run.
div(filename). src/test/resources/arquillian.xml
@@ -548,6 +548,8 @@ bc(prettify).. <arquillian xmlns="http://jboss.org/schema/arquillian"
</engine>
</arquillian>
-p. Run a test, then check the target/deployments folder. You should see a file with the extension .jar or .war, depending on the requirements of the container you are targeting. You can inspect the contents of this file using an archive manager. Hopefully what you find in the archive will provide necessary insight into what classes and resources are available to your test (and why you might be getting a missing class exception).
+p. To enable the export for just a single test, use the VM argument @arquillian.deploymentExportPath@. For example: @-Darquillian.deploymentExportPath=target/deployments/@.
+
+Now run a test and check the target/deployments folder. You should see a file with the extension .jar, .war or .ear. (Arquillian may have packaged the archive defined in the test inside another archive in order to add some magic). You can inspect the contents of this file using an archive manager. Hopefully the contents of the archive will give you the necessary insight to track down class not found or resource missing exceptions.
At this point, you've learned how to run and debug your tests in embedded, remote and managed containers. There's no holding you back now. Keep on writing _real tests_ and make Ike proud!

0 comments on commit 45465b2

Please sign in to comment.