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
{{ message }}
Repository navigation
Commit 7a91bca
Browse filesBrowse the repository at this point in the historyBrowse files
printf '%s\n' 'GitHub-backed IDE tests skip in CI because no GitHub test-user credentials are supplied. They remain available for manually configured runs. Skipped tests do not validate IDE or SSH gateway functionality. See test/README.md.' >> "$GITHUB_STEP_SUMMARY"
printf '%s\n' 'The 13 IDE integration tests skip in this workflow because no GitHub test-user credentials are supplied. They remain available for manually configured runs. Deployment/readiness and skipped-test reports provide no functional IDE or SSH gateway coverage.' >> "$GITHUB_STEP_SUMMARY"
printf '%s\n' 'The workspace creation/image-build smoke test skips in CI because no GitHub test-user credentials are supplied; it remains available manually. Gitpod API smoke tests require explicit opt-in and separate Gitpod credentials, which this workflow does not supply. Skipped-only runs provide no functional smoke coverage.' >> "$GITHUB_STEP_SUMMARY"
Copy file name to clipboardExpand all lines: test/README.md
+31-11Lines changed: 31 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,17 +22,19 @@ Such tests are for example:
22
22
23
23
## Automatically at Gitpod
24
24
25
-
You can opt-in to run the integrations tests as part of the build job. that runs the integration tests against preview environments.
25
+
The **Branch Build** workflow runs webapp tests when the PR description selects:
26
26
27
-
> For tests that require an existing user the framework tries to automatically select one from the DB.
28
-
> - On preview envs make sure to create one before running tests against it!
29
-
> - If it's important to use a certain user (with fixed settings, for example) pass the additional `username` parameter.
27
+
```markdown
28
+
-[x] with-integration-tests=webapp
29
+
```
30
30
31
-
Example command:
31
+
This builds and deploys the branch to a large preview and runs the server/database
32
+
suite. The **Workspace integration tests** workflow always runs `workspace`.
32
33
33
-
```console
34
-
werft job run github -a with-preview=true -a with-integration-tests=webapp -f
35
-
```
34
+
CI does not supply GitHub test-user credentials. Tests requiring them skip;
35
+
other workspace, component, and webapp tests continue to run. Default IDE and
36
+
workspace-creation smoke runs have no functional coverage when all tests skip.
37
+
The implementations and manual entry points remain available.
36
38
37
39
## Manually
38
40
@@ -69,9 +71,27 @@ If you want to run an entire test suite, the easiest is to use `./test/run.sh`:
69
71
70
72
If you're iterating on a single test, the easiest is to use `go test` directly.
71
73
72
-
If your integration tests depends on having having a user token available, then you'll have to set `USER_NAME` and `USER_TOKEN` environment variables. This can be done a couple ways:
73
-
1. Get credentials persisted as secrets (either in Github Actions, or GCP Secret Manager via the `core-dev` project), which vary by job that trigger tests. Refer to `run.sh` for details.
74
-
2. In your Gitpod (preview) environment, log into the preview environment, set `USER_NAME` to the user you logged in with, and set `USER_TOKEN` to any (does not have to be valid).
74
+
For GitHub-backed tests, explicitly supply `USER_NAME` (or `-username`) and
75
+
`USER_TOKEN`, where `USER_TOKEN` is a **GitHub user token**. The runner preserves
76
+
these manual inputs and no longer loads credentials from CI environment aliases
77
+
or the Kubernetes test-user secret. Use a preview with a working GitHub auth
78
+
provider. Disk tests require the selected user to already have a usable GitHub
79
+
identity/token in the preview database; they skip when no username is supplied.
80
+
81
+
```sh
82
+
export USER_NAME='<test username>'
83
+
export USER_TOKEN='<GitHub user token>'
84
+
./test/run.sh -s workspace
85
+
```
86
+
87
+
Without these variables, credential-dependent tests skip and the remaining tests
88
+
use their builtin or temporary user paths. IDE tests retain their additional
89
+
setup requirements; see [JetBrains manual instructions](../dev/jetbrains-test/README.md).
90
+
91
+
The opt-in collaborator smoke tests use `USER_TOKEN` for a different purpose: a
92
+
**Gitpod PAT or session cookie**, with `TEST_COLLABORATOR=true`. Temporary-token
93
+
smoke tests use `INSTALLATION_ADMIN_PAT` / `MEMBER_USER_PAT` and
94
+
`TEST_CREATE_TMP_TOKEN=true`. Those interfaces are unchanged.
0 commit comments