anchor.diff:  /src::
   Contains Go source files
   
  -. Add the path to the root workspacce directory to the _GOPATH_ environment
  +. Add the path of the root workspace directory to the _GOPATH_ environment
   variable. For example:
   +
   ----
  
positive.code: 
  Integration tests utilize https://github.com/DATA-DOG/godog[`godog`], which uses Gherkin (Cucumber)
  to define test cases. The test cases are defined in `test/integration/*.feature`.
  Per default the tests are executed against the binary created by `make build`. This means
  `$GOPATH/bin/minishift`. To run the tests, run:
  
  ----
  $ make integration
  ----
  
  To run integration tests against a Minishift binary in different location you can use the
  `MINISHIFT_BINARY` argument:
  
  ----
  $ make integration MINISHIFT_BINARY=<path-to-custom-binary>
  ----
  
  Additional properties for Godog runner can be specified with `GODOG_OPTS` argument. Following options are available:
  
  - `tags`: when used only scenarios and features containing at least one of selected tags will be executed.
  - `paths`: defines paths to different feature files or folders containing feature files. This can be used to run feature files
  outside of `test/integration/features` folder.
  - `format`:  you can change format of Godog's output, for example you can use `pretty` format instead of native `progress`.
  - `stop-on-failure`: set to true to stop integration tests on failure.
  - `no-colors`: set to true to disable ansi colors of Godog's output.
  - `definitions`: set to true to print all available step definitions.
  
  For example to run integration tests on two specific feature files, using only `@basic` and `@openshift` tags and without ansi colors,
  following command can be used:
  
  ----
  $ make integration GODOG_OPTS="-paths ~/tests/custom.feature,~/my.feature -tags basic,openshift -no-colors true"
  ----
  
  NOTE: When multiple values are used for options in GODOG_OPTS, then those have to be separated with
  comma without a whitespace.
  While `-tags basic,openshift` will be parsed properly by make, whereas `-tags basic, openshift` will
  result in only `@basic` being used.
  
  [[format-source]]
  === Formatting the source
  
  Minishift adheres to the Go formatting https://golang.org/doc/effective_go.html#formatting[guidelines].
  Code with incorrect formatting will fail the the CI builds. You can check whether any of your
  files violate the guidelines with the following command:
  
  ----
  $ make fmtcheck
  ----
  
  You can correct the formatting errors yourself ot instruct the violations to be corrected automatically
  with the following command:
  
  ----
  
negative.code: 
  [NOTE]
  ====
  On Windows you might encounter errors because some of the dependency path names are too long. +
  Workaround: Use a non-default `tmp` directory for Glide to shorten the path length.
  
  ----
  