tests for implemented flows (username password)

[hifabienne]

As ZITADEL Admins we want to ensure that all of the implemented oidc flows always work with the current ZITADEL Cloud version.

Acceptance Criteria

• Flow
  • User enters username
  • User enters password
  • User is redirected to app
• Token has expected claims (have a look at current token and take those claims, so we have a starting point)
• PRs can only be merged if e2e tests succeed (test against latest ZITADEL docker)
• Nightly e2e tests ensure we detect breaking cloud version changes early
• Tests don't rely on results of other tests

Test Cases:
Given: Username password login is enabled

• Login with username without suffix
• Login with username with suffix
• Login with email address
• Login with phone
• Login with disabled user --> error
• Login with locker user -->
• Not existing username --> error
• Wrong password --> error

Open Questions

How do we want to run the e2e tests?
To preview deployement?
In the pipeline?

[eliobischof]

I would add to the AC:

• PRs can only be merged if e2e tests succeed
• Nightly e2e tests ensure we detect breaking cloud version changes early

Estimation: 3

[peintnermax]

I would add to the AC:

• PRs can only be merged if e2e tests succeed
• Nightly e2e tests ensure we detect breaking cloud version changes early

Estimation: 3

agree 👍