Description

Migrate Keycloak E2E tests to workspaces/keycloak/e2e-tests/.

Setup Prerequisites

Keycloak Instance: Running Keycloak server with configured realm

• KEYCLOAK_BASE_URL: Keycloak server URL
• KEYCLOAK_LOGIN_REALM, KEYCLOAK_REALM: Realm names
• KEYCLOAK_CLIENT_ID, KEYCLOAK_CLIENT_SECRET: OIDC client credentials

Based on RHDH core config (.ibm/pipelines/resources/config_map/app-config-rhdh.yaml):

catalog:
  providers:
    keycloakOrg:
      default:
        baseUrl: ${KEYCLOAK_BASE_URL}
        loginRealm: ${KEYCLOAK_LOGIN_REALM}
        realm: ${KEYCLOAK_REALM}
        clientId: ${KEYCLOAK_CLIENT_ID}
        clientSecret: ${KEYCLOAK_CLIENT_SECRET}
        schedule:
          frequency: { minutes: 60 }
          initialDelay: { seconds: 15 }
          timeout: { minutes: 50 }

Keycloak Users/Groups: Pre-configured users and groups in the realm for testing

Source Files (RHDH Core)

Plugin Packages

Acceptance Criteria

1. Create Workspace Structure

• [ ] Create workspaces/keycloak/e2e-tests/
• [ ] Copy standard config files from tech-radar reference
• [ ] Update package.json name and playwright.config.ts project name

2. Create RHDH Configuration (tests/config/)

• [ ] Create dynamic-plugins.yaml based on RHDH core dynamic-plugins.default.yaml
• [ ] Create rhdh-secrets.yaml based on RHDH core .ibm/pipelines/auth/secrets-rhdh-secrets.yaml

3. Migrate Test Files

• [ ] Create tests/specs/catalog-users.spec.ts

4. Verify All Tests Pass

• [ ] All 2 test cases pass

Test Cases (2 total)

1-2. Keycloak catalog users tests

Reference

• Template: workspaces/tech-radar/e2e-tests