anchor.diff:  </plugin>
   ----
   
  -Then, create the `src/test/java/org/acme/quickstart/GreetingResourceIT.java` with the following content:
  +This instructs the failsafe-maven-plugin to run integration-test and indicates the location of the produced native executable.
  +
  +Then, open the `src/test/java/org/acme/quickstart/NativeGreetingResourceIT.java`. It contains:
   
   [source,java]
   ----
  
positive.code: [INFO]  T E S T S
  [INFO] -------------------------------------------------------
  [INFO] Running org.acme.quickstart.GreetingResourceIT
  Executing [/Users/starksm/Dev/JBoss/Quarkus/starksm64-quarkus-quickstarts/getting-started-native/target/quarkus-quickstart-runner, -Dquarkus.http.port=8081, -Dtest.url=http://localhost:8081, -Dquarkus.log.file.path=target/quarkus.log]
  2019-02-28 16:52:42,020 INFO  [io.quarkus] (main) Quarkus started in 0.007s. Listening on: http://localhost:8080
  2019-02-28 16:52:42,021 INFO  [io.quarkus] (main) Installed features: [cdi, resteasy]
  [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.081 s - in org.acme.quickstart.GreetingResourceIT
  
negative.code: 
  Producing a native executable can lead to a few issues, and so it's also a good idea to run some tests against the application running in the native file.
  
  In the `pom.xml` file, the `native` profile contains:
  
  [source, xml]
  ----
  