You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tests/integration/README.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,22 @@
1
1
# Integration Tests
2
+
2
3
Package for defining integration tests. Currently, there is a setup for API and Orchestrator testing.
3
4
4
5
## Run locally
5
-
1) Setup env variables in the .env file
6
-
2) If necessary, run `make connect-orchestrator` to create a tunnel to one orchestrator client VM in GCP
7
-
3) Run `make test`
6
+
7
+
1. Setup env variables in the root folder `infra/.env` file
8
+
2. If you made changes to the `api` or `envd` protobuf spec, run `make generate` from this folder (and don't forget to generate it in `envd` if changes apply there too).
9
+
3. If necessary, run `make connect-orchestrator` to create a tunnel to one orchestrator client VM in GCP (you may need to run `make setup-ssh` the first time)
10
+
4. Run `make test` in this folder or `make test-integration` from the root `infra/` folder.
8
11
9
12
## Usage of clients (api, orchestrator, envd)
13
+
10
14
All tests are in the folder internal/tests. You can see the usage of different clients in the tests. Here are just basics.
11
15
12
16
### API
17
+
13
18
HTTP client. In order to pass the API key, use the `setup.WithAPIKey()` option.
0 commit comments