@@ -135,9 +135,13 @@ Run the integration tests with:

     $ hack/test-integration.sh

 The script launches an instance of etcd and then invokes the integration tests. If you need to

-execute an individual test start etcd and then run:

+execute a subset of integration tests, run:

-    $ hack/test-go.sh test/integration -tags 'integration no-docker' -test.run=TestBuildClient

+    $ hack/test-integration.sh <regex>

+    

+Where `<regex>` is some regular expression that matches the names of all of the tests you want to run.

+The regular expression is passed into `grep -E`, so ensure that the syntax or features you use are supported.

+The default regular expression used is `Test`, which matches all tests.

 Each integration function is executed in its own process so that it cleanly shuts down any background

 goroutines. You will not be able to run more than a single test within a single process.

@@ -343,7 +347,8 @@ OpenShift integrates the go `pprof` tooling to make it easy to capture CPU and h

   * `mem` - generate a running heap dump that tracks allocations to `./mem.pprof`

   * `web` - start the pprof webserver in process at http://127.0.0.1:6060/debug/pprof (you can open this in a browser)

-    # start the server in CPU profiling mode

+In order to start the server in CPU profiling mode, run: 

+

     $ OPENSHIFT_PROFILE=cpu sudo ./_output/local/go/bin/openshift start

 To view profiles, you use [pprof] which is part of `go tool`.  You must pass the binary you are debugging (for symbols) and a captured pprof.  For instance, to view a `cpu` profile from above, you would run OpenShift to completion, and then run:

@@ -384,4 +389,4 @@ Finally, when using the `web` profile mode, you can have the go tool directly fe

     # for a snapshot heap dump at the current time, showing total allocations

     $ go tool pprof --alloc_space ./_output/local/go/bin/openshift http://127.0.0.1:6060/debug/pprof/heap

-See [debugging Go programs](https://golang.org/pkg/net/http/pprof/) for more info.  `pprof` has many modes and is very powerful (try `tree`) - you can pass a regex to many arguments to limit your results to only those samples that match the regex (basically the function name or the call stack).

\ No newline at end of file

+See [debugging Go programs](https://golang.org/pkg/net/http/pprof/) for more info.  `pprof` has many modes and is very powerful (try `tree`) - you can pass a regex to many arguments to limit your results to only those samples that match the regex (basically the function name or the call stack).