anchor.diff:                                  server.getPassword());
   ----
   
  -Here is the complete test class after modification :
  +Once modified, the complete test class looks as follows:
   [source,java,indent=0,subs="verbatim,quotes,attributes",role="initial-block-closed"]
   ----
   public class SearchTest {
  
positive.code: }
  ----
  
  *This test will continue to work in simulation mode.* as we have our API simulation proxy activated.
  
  == Set up CI server in passthrough mode
  Let's make it work in real mode on a CI server. we will use https://jenkins.io/[jenkins] in this tutorial
  
  Log in to your jenkins then : Click on *New Item* to create a new build job
  
  image::jenkins/1_jenkins_new_item.png[Create a new job]
  
  Enter an Item name (Job name) and choose the freestyle job. Then click OK.
  
  image::jenkins/2_jenkins_new_item.png[Create a new job]
  
  In *Source Code Management* section enter your project repository URL. We are using our github repository in this tutorial.
  We will build the `master` branch
  
  image::jenkins/4_jenkins_source_code.png[Source Code Management]
  
  In the *Build Section* click on *add build step*, then choose *Invoke top-level Maven targets*
  
  image::jenkins/6_jenkins_build_cmd.png[Build Section]
  
  Choose you Maven version, and enter your maven build command. we are using a simple `clean install` and click *save*.
  
  image::jenkins/6_jenkins_build_cmd_2.png[Build Section]
  
  You can notice that we have added the option `-Dtalend.junit.http.passthrough=true` to our build command.
  This Option will tell the API simulation proxy to run in `passthrough` mode. So it's will forward all the http request
  that we have maded in our test to the real API server.
  
  We also get the real credentials, thanks to our `MavenDecrypterRule` rule.
  
  TIP: You can configure the *passthrough* mode globally on your CI server by setting the environment variable `talend.junit.http.passthrough`
  to `true`.
  
  6.Test the job. click *Build now* you can notice that your job have built correctly.
  
  image::jenkins/7_jenkins_build_result.png[Test the job]
  
  
  That's all you need to do, now your tests run in a simulation mode on dev and in a (passthrough) mode on your CI server.
negative.code: = Testing in a Continuous Integration environment
  :page-partial:
  
  [[tutorial-dev-vs-ci-setup.adoc]]
  
  This tutorial shows how to adapt the test configuration of the Zendesk search component that was done in xref:tutorial-test-rest-api.adoc[this previous tutorial] to make it work in a Continuous Integration environment.
  
  In the test, the Zendesk credentials are used directly in the code to perform a first capture of the API response. Then, fake credentials are used in the simulation mode because the real API is not called anymore.
  
  However, in some cases, you can require to continue calling the real API on a CI server or on a specific environment.
  
  To do that, you can adapt the test to get the credentials depending on the execution mode (simulation/passthrough).
  
  == Setting up credentials
  These instructions concern the CI server or on any environment that requires real credentials.
  
  This tutorial uses:
  
  - A https://maven.apache.org/guides/mini/guide-encryption.html[Maven server] that supports password encryption as a credential provider. Encryption is optional but recommended.
  - The `MavenDecrypterRule` test rule provided by the framework. This rule lets you get credentials from Maven settings using a server ID.
  
  To create encrypted server credentials for the Zendesk instance:
  
  1. Create a master password using the command: `mvn --encrypt-master-password <password>`.
  2. Store this master password in the `settings-security.xml` file of the `~/.m2` folder.
  3. Encrypt the Zendesk instance password using the command: `mvn --encrypt-password <zendesk-password>`.
  4. Create a server entry under *servers* in Maven `settings.xml` file located in the `~/.m2` folder.
  [source,xml]
  ----
      <server>
        <id>zendesk</id>
        <username>username@email.com</username>
        <password>The encrypted password {oL37x/xiSvwtlhrMQ=}</password>
      </server>
  ----
  
  NOTE: You can store the `settings-security.xml` and `settings.xml` files elsewhere that the default location (`~/.m2`). To do that, set the path of the directory containing the files
  in the `talend.maven.decrypter.m2.location` environment variable.
  
  == Adapting the unit test
  . Add the `MavenDecrypterRule` rule to the test class. This rule allows to inject server information stored in Maven `settings.xml` file to the test. The rule also decrypts credentials if they are encrypted.
  
  [source,java,indent=0,subs="verbatim,quotes,attributes",]
  ----
  public class SearchTest {
  