anchor.diff:  . Push both branches to your remote repository.
   . Run the tests with `./gradlew check -Dtests.bwc.remote=${remote} -Dtests.bwc.refspec.5.x=index_req_bwc_5.x`.
   
  -== Skip fetching latest
  +==== Skip fetching latest
   
   For some BWC testing scenarios, you want to use the local clone of the
   repository without fetching latest. For these use cases, you can set the system
  
positive.code: == Testing backwards compatibility
  
  Backwards compatibility tests exist to test upgrading from each supported version
  to the current version. To run all backcompat tests use:
  
  -------------------------------------------------
  ./gradlew bwcTest
  -------------------------------------------------
  
  A specific version can be tested as well. For example, to test backcompat with
  version 5.3.2 run:
  
  -------------------------------------------------
  ./gradlew v5.3.2#bwcTest
  -------------------------------------------------
  
  When running `./gradlew check`, some minimal backcompat checks are run. Which version
  is tested depends on the branch. On master, this will test against the current
  stable branch. On the stable branch, it will test against the latest release
  branch. Finally, on a release branch, it will test against the most recent release.
  
  === BWC Testing against a specific remote/branch
  
  Sometimes a backward compatibility change spans two versions. A common case is a new functionality
  that needs a BWC bridge in an unreleased versioned of a release branch (for example, 5.x).
  
negative.code: # enable security debugging
  ./gradlew test -Dtests.jvm.argline="-Djava.security.debug=access,failure"
  ------------------------------
  
  == Running verification tasks
  
  