anchor.diff:  [source,groovy,indent=0]
   ----
   dependencies {
  -    contracts "${conractsGroupId}:${contractsArtifactId}:${contractsVersion}"
  -    testCompile "${conractsGroupId}:${contractsArtifactId}:${contractsVersion}"
  +    contracts "${contractsGroupId}:${contractsArtifactId}:${contractsVersion}"
  +    testCompile "${contractsGroupId}:${contractsArtifactId}:${contractsVersion}"
   }
   ----
   ====
  
positive.code: [source,groovy,indent=0]
  ----
  ext {
      conractsGroupId = "com.example"
      contractsArtifactId = "common-repo"
      contractsVersion = "1.2.3"
  }
  
negative.code: 
  If a contract is in progress, it means that the on the producer side tests will not be generated, but the stub will be. You can read more about this in <<project-features.adoc#contract-dsl-in-progress, this section>> of the documentation.
  
  In a CI build, before going to production, you would like to ensure that no in progress contracts are there on the classpath. That's because you may lead to false positives. That's why, by default, in the Spring Cloud Contract plugin, we set the value of `failOnInProgress` to `true`. If you want to allow such contracts when tests are to be generated, just set the flag to `false`.
  