Skip to content

fix: improve e2e to not conflict when run in parallel#894

Open
JoaoBraveCoding wants to merge 2 commits intoobservatorium:mainfrom
JoaoBraveCoding:fix-e2e-flaky
Open

fix: improve e2e to not conflict when run in parallel#894
JoaoBraveCoding wants to merge 2 commits intoobservatorium:mainfrom
JoaoBraveCoding:fix-e2e-flaky

Conversation

@JoaoBraveCoding
Copy link
Copy Markdown
Contributor

@JoaoBraveCoding JoaoBraveCoding commented Mar 31, 2026

Improve e2e tests by:

  • Properly isolate Docker networks for parallel integration tests
  • fix Dex token TLS verification for test CA and CI

@JoaoBraveCoding JoaoBraveCoding changed the title fix: improve e2e to not conflict when run in parallel WIP fix: improve e2e to not conflict when run in parallel Mar 31, 2026
Use a per-test network name derived from t.Name() with e2e.WithName, since bare
e2e.New() hashes runtime.Caller(3) and collides on testing.tRunner for every
test. Derive TLS/OIDC hostnames from e.Name() via getContainerName, drop fixed
env name constants, and align Dex/tenant API host with the observatorium-api
runnable.
Sign leaves with the parsed CA so AuthorityKeyId matches SubjectKeyId on ca.pem.
Add host.docker.internal to Dex/API SANs, set tls.ServerName to the Dex Docker
hostname when posting to dex/token, and fail if ca.pem does not parse into the
root pool.
@JoaoBraveCoding JoaoBraveCoding changed the title WIP fix: improve e2e to not conflict when run in parallel fix: improve e2e to not conflict when run in parallel Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant