This updates the test-ci target to startup the test database container
first, wait for it to be ready, and then start running the tests.
It also creates some new targets for local devs. Prior to running any
tests either via `make test` or `go test`, the database should be
started with:
make test-database-up
It can take a few seconds for the database to fully initialize, the
status can be checked with:
docker logs -f boundary-sql-tests
This database can be stopped and destroyed with:
make test-database-down
In general it should only need to be restarted when new migrations are
added. But it might also be necessary to restart if some tests fail in
an unexpected way and fail to do cleanup steps.
* docs: update contributing guide with pronoun expectation and link to community guidelines
* Update CONTRIBUTING.md
Co-authored-by: Jasmine Dahilig <jasmine@dahilig.com>
Co-authored-by: Jasmine Dahilig <jasmine@dahilig.com>
Timothy Messier
Jeff MalnickandJasmine Dahilig
s-christoff
Jim