Add testing section for individual/user testing (#927)

build-9761f1deee3fceeb4e9a11696e3a15de813c6979-eee4aa2684a7d81e
s-christoff 5 years ago committed by GitHub
parent bab647b5e2
commit 5dc821a41e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -66,4 +66,24 @@ Any enhancements, new features, etc fall into this section.
Any bug fixes fall into this section.
## Testing
To run the entire test suite run this command in the root of the project:
```
$ make test
```
Before running any test please ensure that Docker is started. Boundary uses a Docker container to initiate a database for testing.
If a test is interrupted check to make certain that all Docker containers have been properly destroyed.
### Running individual tests
If you don't want to run the entire test suite, you can just run a singe test
with go. For example, if you wanted to run the tests TestAuthTokenAuthenticator, you would
run:
```
$ go test -run TestAuthTokenAuthenticator -v ./internal/auth
```

@ -148,6 +148,9 @@ website-start:
test-ci: install-go
~/.go/bin/go test ./... -v $(TESTARGS) -timeout 120m
test:
~/.go/bin/go test ./... -timeout 30m
install-go:
./ci/goinstall.sh

@ -1,5 +1,5 @@
# Boundary
![](boundary.png)
![](boundary.png) [![CircleCI](https://circleci.com/gh/hashicorp/boundary/tree/main.svg?style=svg)](https://circleci.com/gh/hashicorp/boundary/tree/main)
----
**Please note**: We take Boundary's security and our users' trust very
@ -204,3 +204,8 @@ could be taken in a production context:
There are many, many more things that Boundary will do in the future in terms of
integrations, features, and more. We have a long roadmap planned out, so stay
tuned for information about new features and capabilities!
## Contributing
Thank you for your interest in contributing! Please refer to
[CONTRIBUTING.md](https://github.com/hashicorp/boundary/blob/main/CONTRIBUTING.md) for guidance.

Loading…
Cancel
Save