README: Enhancement for OTE

Adding descriptions for building the binary and running the tests

Author: JianLi-RH

cmd/cluster-version-operator-tests/README.md

@@ -4,22 +4,39 @@ It integrates [openshift-tests-extension](https://github.com/openshift-eng/opens
 cluster-version-operator which allows openshift components to contribute tests to openshift-tests' suites with
 extension binaries.
 
+## Build the executable binary
+In root folder, run below command to build executable binary:
+```console
+$ make build
+```
 
 ## Run the tests locally
 
-## Using the framework
+### Using the binary
+- run a test-suite
 ```console
-$ hack/build-go.sh
-$ _output/<OS>/<ARCH>/cluster-version-operator-tests run-suite cluster-version-operator
+$ _output/<OS>/<ARCH>/cluster-version-operator-tests run-suite <test suite name>
 ```
+where test suites can be listed by `_output/<OS>/<ARCH>/cluster-version-operator-tests info`.
 
-## Using ginko-cli
+- run a single test case
+```console
+$ _output/<OS>/<ARCH>/cluster-version-operator-tests run-test <test case name>
+```
+where test names can be listed by `_output/<OS>/<ARCH>/cluster-version-operator-tests list`.
+
+### Using ginkgo-cli
 
 After [installing-ginkgo](https://onsi.github.io/ginkgo/#installing-ginkgo):
 
 ```console
 $ ginkgo ./test/...
 ```
+or run a specific test
+```console
+$ ginkgo --focus "<test case name>" ./test/...
+```
+`test case name` is the text in g.It()
 
 The output looks nicer this way.