gorc
gorc copied to clipboard
Recursive go testing, done better.
Hello, I've seen that this project has seen its last commit in 2013. That seems fairly outdated. So before we opt in to use it we would like to know...
This is the output im getting. Something is not right with the repository I guess? $ git clone [email protected]:stretchr/gorc.git Cloning into 'gorc'... remote: Counting objects: 368, done. remote: Total 368...
`gorc test assert mock` would find the packages and run the tests for both packages. Currently only one is supported.
Would be great for gorc to monitor files for changes, and automagically re-run the tests whenever anything changes.
It may be nice to be able to define a set of packages under a given name and then execute that set of tests by passing the set name. For...
Currently we run a separate go command for every found package. The go command supports multiple packages being passed. For example: `go test . ./assert ./mock` Will run tests against...
If a directory is hidden (begins with .), ignore it. .hg and .git should never be traversed.
Use an approach similar to this blog post by Dave Cheney: http://dave.cheney.net/2013/06/19/stress-test-your-go-packages gorc stress
- instead of running ALL tests, only run tests on packages that have changed