Skip to content

Commit bcdcdaa

Browse files
committed
[test] A documentation on how to run the werft job
1 parent 10e2539 commit bcdcdaa

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

test/README.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,17 @@ Such tests are for example:
1515
- instrumentation: agents that are compiled before/during the test, uploaded to a pod and executed there.
1616
They communicate with the test using net/rpc.
1717
- API access: to all internal APIs, including ws-manager, ws-daemon, image-builder, registry-facade, server
18-
- DB access to the Gitpod DB
18+
- DB access to the Gitpod DB
19+
20+
## Run
21+
22+
There is a [werft job](../.werft/run-integration-tests.yaml) that runs the integration tests against `core-dev` preview environments.
23+
24+
> For tests that require an existing user the framework tries to automatically select one from the DB.
25+
> - On preview envs make sure to create one before running tests against it!
26+
> - If it's important to use a certain user (with fixed settings, for example) pass the additional `username` parameter.
27+
28+
Example command:
29+
```
30+
werft job run github -j .werft/run-integration-tests.yaml -a namespace=staging-gpl-2658-int-tests -a version=gpl-2658-int-tests.57 -f
31+
```

0 commit comments

Comments
 (0)