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: Development vs Continuous integration Setup
  
  :page-partial:
  
  [[tutorial-dev-vs-ci-setup.adoc]]
  
  xref:tutorial-test-rest-api.adoc[In a previous tutorial], we have shown how to create a mocked test for our Zendesk search component.
  
  In the test you can notice that we have used our Zendesk credentials directly into the code to do a first capture of the API response,
  then we have switched to a fake credentials in simulation mode as we do not call the real API anymore.
  
  *But what if you want to continue to call the real API on the CI server or on a a specific environment ?*
  
  Let's make our test able to get the credentials depending on the execution mode (simulation/passthrough).
  
  == Credentials setup
  IMPORTANT: This instructions, need to be done, on the CI server or on any environment that require the real credentials.
  
  We will use https://maven.apache.org/guides/mini/guide-encryption.html[Maven servers, that support password encryption] as a credentials provider,
  and the test rule `MavenDecrypterRule` provided by the framework.
  
  This rule let you get credentials from maven settings using a server id.
  
  So let's create an encrypted server credential for our zendesk instance.
  
  1. Create a master password using the command : `mvn --encrypt-master-password <password>`
  2. Store this master password in `settings-security.xml` file  in `~/.m2` folder.
  3. Encrypt zendesk instance password using the command: `mvn --encrypt-password <zendesk-password>`
  4. Create a server entry under *servers* in maven `settings.xml` file in `~/.m2`.
  [source,xml]
  ----
      <server>
        <id>zendesk</id>
        <username>username@email.com</username>
        <password>The enccrypted password {oL37x/xiSvwtlhrMQ=}</password>
      </server>
  ----
  
  NOTE: Encryption is optional but recommended.
  
  TIP: If you want to store the `settings-security.xml` and `settings.xml` files elsewhere that the default location `~/.m2`.
  You can do it by setting the path of the directory containing the files
  into the environment variable  `talend.maven.decrypter.m2.location`
  
  == Let's adapt our unit test to use the credentials from maven servers
  We start by adding `MavenDecrypterRule` rule to our test class. This rule will let us inject server information stored
  in maven settings.xml to our test. The rule will also decrypt the password if they are encrypted.
  [source,java,indent=0,subs="verbatim,quotes,attributes",]
  ----
  public class SearchTest {
  
negative.code:     public final MavenDecrypterRule mavenDecrypterRule = new MavenDecrypterRule(this);
  }
  ----
  
  [start=2]
  . Inject the Zendesk server to the test. To do that, add a new field to the class with the `@DecryptedServer` annotation, that holds the server ID to be injected.
  
  [source,java,indent=0,subs="verbatim,quotes,attributes",]
  ----
  public class SearchTest {
  