Skip to content
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.

Commit

Permalink
add new make targets to README
Browse files Browse the repository at this point in the history
Also adds missing information to README about $PATHs

Signed-off-by: Charlie Wheeler-Robinson <cwheeler@redhat.com>
  • Loading branch information
crwr45 authored and ryandgoulding committed Jan 12, 2021
1 parent 93f1d3a commit f532bb1
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ certification. Please see "CNF Developers" below for more information.

## Dependencies

At a minimum, the following dependencies must be installed *prior* to running `make dependencies`.
At a minimum, the following dependencies must be installed *prior* to running `make deps-install`.

Dependency|Minimum Version
---|---
Expand All @@ -22,9 +22,11 @@ Dependency|Minimum Version
All other dependencies required to run tests can be installed using the following command:

```shell-script
make dependencies
make deps-install
```

*Note*: You must also make sure that `$GOBIN` (default `$GOPATH/bin`) is on your `$PATH`.

*Note*: Efforts to containerize this offering are considered a work in progress.

## Available Test Specs
Expand Down Expand Up @@ -81,9 +83,7 @@ In order to build the test executable, first make sure you have satisfied the [d
make build-cnf-tests
```

If a build fails after `go get github.com/onsi/ginkgo/ginkgo`, add ginkgo location to the PATH: `export PATH=$PATH:~/go/bin`

*Gotcha:* The `make build` command runs the unit tests for the framework, it does NOT test the CNF.
*Gotcha:* The `make build*` commands run unit tests where appropriate. They do NOT test the CNF.

### Testing a CNF

Expand Down

0 comments on commit f532bb1

Please sign in to comment.