zitadel/internal/integration
Tim Möhlmann 10d5fc6184
test: no location header in response (#8441)
# Which Problems Are Solved

Sometimes integrations tests are failing with an error `http: no
location header in response`. The underlying cause was hidden, as in
some tests we assumed a 3xx range response but got a 4xx response
instead. No assertion on the status code was made, resulting in the
above error message on calling `resp.Location()`.

The underlying issue, the application not found in the projection, is
also fixed.

# How the Problems Are Solved

This change adds a check for the status code and returns the response
body if the response is not in the 3xx status code range.

Helper function that create applications now do an additional
`GetAppByID` in a retry loop to ensure consitency in the projection
before proceeding with tests.

# Additional Changes

- none

# Additional Context

- Pipline failures were observed, no issue was created
- Cherry-picked form WIP #8407

Co-authored-by: Livio Spring <livio.a@gmail.com>
2024-08-17 14:48:06 +00:00
..
config refactor(database): exchange connection pool (#8325) 2024-07-17 15:16:02 +00:00
assert_test.go feat: impersonation roles (#7442) 2024-02-28 10:21:11 +00:00
assert.go feat(v3alpha): read actions (#8357) 2024-08-12 22:32:01 +02:00
client.go feat: org v2 ListOrganizations (#8411) 2024-08-15 06:37:06 +02:00
integration_test.go AddHumanUser tests 2023-04-28 14:39:53 +03:00
integration.go test: no location header in response (#8441) 2024-08-17 14:48:06 +00:00
oidc.go test: no location header in response (#8441) 2024-08-17 14:48:06 +00:00
rand.go feat: restrict languages (#6931) 2023-12-05 11:12:01 +00:00
user.go feat(oidc): token exchange impersonation (#7516) 2024-03-20 10:18:46 +00:00
usertype_string.go feat(api): add organisation service (#6340) 2023-08-11 14:19:14 +00:00