Switch to ginkgo/gomega for tests

This switches over to ginkgo/gomega for tests, which makes writing
certain tests easier/more fluent in the future.
This commit is contained in:
Solly Ross 2018-09-25 14:27:33 -04:00
parent c5801455ec
commit cc08a1fb41
260 changed files with 184637 additions and 6412 deletions

12
vendor/github.com/onsi/gomega/RELEASING.md generated vendored Normal file
View file

@ -0,0 +1,12 @@
A Gomega release is a tagged sha and a GitHub release. To cut a release:
1. Ensure CHANGELOG.md is up to date.
- Use `git log --pretty=format:'- %s [%h]' HEAD...vX.X.X` to list all the commits since the last release
- Categorize the changes into
- Breaking Changes (requires a major version)
- New Features (minor version)
- Fixes (fix version)
- Maintenance (which in general should not be mentioned in `CHANGELOG.md` as they have no user impact)
2. Update GOMEGA_VERSION in `gomega_dsl.go`
3. Push a commit with the version number as the commit message (e.g. `v1.3.0`)
4. Create a new [GitHub release](https://help.github.com/articles/creating-releases/) with the version number as the tag (e.g. `v1.3.0`). List the key changes in the release notes.