From c1ab029745520914fae525f150e91dfe7ae76142 Mon Sep 17 00:00:00 2001 From: Wyatt Anderson Date: Wed, 21 Jun 2017 02:29:17 -0400 Subject: [PATCH] docs: update test command in README and CONTRIBUTING (#183) Signed-off-by: Wyatt Anderson --- CONTRIBUTING.md | 2 +- README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e869527cf..ffd0dee30 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -96,7 +96,7 @@ To make a pull request, you will need a GitHub account; if you are unclear on th 1. Create a feature branch off of `master` so that changes do not get mixed up. 1. [Rebase](https://git-scm.com/book/en/Git-Branching-Rebasing) your local changes against the `master` branch. -1. Run the full project test suite with the `go test ./...` (or equivalent) command and confirm that it passes. +1. Run the full project test suite with the `go test $(glide novendor)` (or equivalent) command and confirm that it passes. 1. Run `gofmt -s` (if the project is written in Go). 1. Accept the Developer's Certificate of Origin on all commits (see above). 1. Ensure that each commit has a subsystem prefix (ex: `controller: `). diff --git a/README.md b/README.md index da4432714..2791e38a0 100644 --- a/README.md +++ b/README.md @@ -351,10 +351,10 @@ go get -d github.com/ory/fosite cd $GOPATH/src/github.com/ory/fosite git status git remote add myfork -go test ./... +go test $(glide novendor) ``` -Simple, right? Now you are ready to go! Make sure to run `go test ./...` often, detecting problems with your code +Simple, right? Now you are ready to go! Make sure to run `go test $(glide novendor)` often, detecting problems with your code rather sooner than later. Please read [CONTRIBUTE.md] before creating pull requests and issues. ### Refresh mock objects