Mode: in-container

@Deployment(testable = true)

As we mentioned above, we need to repackage your @Deployment, adding some Arquillian support classes, to run in-container. This gives us the ability to communicate with the test, enrich the test and run the test remotely. In this mode, the test executes in the remote container; Arqullian uses this mode by default.

See the Complete Protocol Reference for an overview of the expected output of the packaging process when you provide a @Deployment.

Mode: as-client

@Deployment(testable = false)

Now this mode is the easy part. As opposed to in-container mode which repackages and overrides the test execution, the as-client mode does as little as possible. It does not repackage your @Deployment nor does it forward the test execution to a remote server. Your test case is running in your JVM as expected and you're free to test the container from the outside, as your clients see it. The only thing Arquillian does is to control the lifecycle of your @Deployment.

Here is an example calling a Servlet using the as client mode.

@RunWith(Arquillian.class)
public class LocalRunServletTestCase
{
   @Deployment(testable = false)
   public static WebArchive createDeployment()
   {
      return ShrinkWrap.create(WebArchive.class, "test.war")
               .addClass(TestServlet.class);
   }

   @Test
   public void shouldBeAbleToCallServlet(@ArquillianResource(TestServlet.class) URL baseUrl) throws Exception
   {
   	  // http://localhost:8080/test/
      String body = readAllAndClose(new URL(baseUrl, "/Test").openStream());

      Assert.assertEquals(
            "Verify that the servlet was deployed and returns the expected result",
            "hello",
            body);
   }
}

Mode: mixed

@Deployment(testable = true)
public static WebArchive create()
{
}

@Test // runs in container
public void shouldBeAbleToRunOnContainerSide() throws Exception
{
}

@Test @RunAsClient // runs as client
public void shouldBeAbleToRunOnClientSide() throws Exception
{
}

It is also possible to mix the two run modes within the same test class. If you have defined the Deployment to be testable, you can specify the @Test method to use run mode as client by using the @RunAsClient annotation. This will allow two method within the same test class to run in different modes. This can be useful if you in a run as client mode want to execute against a remote endpoint in your application, for then in the next test method assert on server side state the remote endpoint migh thave created.