rhdh / rules

---
---

# RHDH (Red Hat Developer Hub) Repository Context

This document serves as a comprehensive starting point for LLMs working with the RHDH repository. It provides detailed information about the e2e-tests, testing infrastructure and CI/CD pipeline.

## Table of Contents

- [E2E Testing Framework](#e2e-testing-framework)
- [CI/CD Infrastructure](#cicd-infrastructure)
- [Key Dependencies and Common Issues](#key-dependencies-and-common-issues)
- [Documentation References](#documentation-references)

## E2E Testing Framework

### Technology Stack
- **Testing Framework**: Playwright with TypeScript
- **Node.js Version**: Use `engines.node` in `e2e-tests/package.json`
- **Package Manager**: Use `packageManager` in `e2e-tests/package.json`
- **Test Runner**: Playwright Test
- **Reporting**: HTML, JUnit XML, List reporters

Current versions for e2e-tests are defined in `e2e-tests/package.json`

### Test Structure and Organization

#### Directory Structure
```text
e2e-tests/
├── playwright/
│   ├── e2e/                    # Main test files
│   │   └── *.spec.ts          # General test files
│   ├── utils/                 # Test utilities
│   ├── data/                  # Test data
│   └── support/               # Test support files
```

#### Test File Requirements

**Component Assignment**: Every test file (`*.spec.ts`) in the `e2e-tests` folder must have a component assigned in the `test.beforeAll` hook using the following syntax:

```typescript
test.beforeAll(async ({ }, testInfo) => {
  testInfo.annotations.push({
    type: "component",
    description: "your_value",
  });
});
```

**Purpose**: This component annotation is used for test categorization, reporting, and CI/CD pipeline organization. It helps identify which component or feature area each test file is validating.

**Examples of Component Values**:
- `"authentication"` - for authentication provider tests
- `"rbac"` - for role-based access control tests
- `"plugins"` - for plugin functionality tests
- `"configuration"` - for configuration validation tests
- `"audit-log"` - for audit logging tests
- `"core"` - for core functionality tests
- `"navigation"` - for navigation and routing tests
- `"api"` - for API endpoint and integration tests
- `"integration"` - for external service integration tests
- `"monitoring"` - for monitoring and observability tests
- `"data-management"` - for data handling and management tests

**Note**: The component description should be descriptive and consistent across related test files to ensure proper test organization and reporting.

#### Key Test Categories

1. **Smoke Tests** (`smoke-test.spec.ts`)
   - Basic functionality verification
   - Health checks and core features

2. **Showcase Tests** (defined in `e2e-tests/playwright/projects.json`)
   - `showcase`: General functionality tests with base deployment using Helm chart
   - `showcase-rbac`: General functionality tests with RBAC-enabled deployment using Helm chart
   - `showcase-k8s`: Kubernetes integration tests with base deployment
   - `showcase-rbac-k8s`: Kubernetes integration tests with RBAC-enabled deployment
   - `showcase-operator`: General functionality tests with base deployment using Operator
   - `showcase-operator-rbac`: General functionality tests with RBAC-enabled deployment using Operator
   - `showcase-runtime`: Runtime environment tests
   - `showcase-sanity-plugins`: Plugin sanity checks
   - `showcase-upgrade`: Upgrade scenario tests
   - `showcase-localization-de`: German localization tests
   - `showcase-localization-es`: Spanish localization tests
   - `showcase-localization-fr`: French localization tests
   - `showcase-localization-it`: Italian localization tests
   - `showcase-localization-ja`: Japanese localization tests
   - `any-test`: Use for debugging when you need to run a specific test

   **Note**: All project names are defined in `e2e-tests/playwright/projects.json` as the single source of truth. This file is consumed by:
   - `playwright.config.ts` via TypeScript import (`e2e-tests/playwright/projects.ts`)
   - CI/CD scripts via `.ci/pipelines/playwright-projects.sh` (exports as `$PW_PROJECT_*` variables)

3. **Authentication Provider Tests** (`showcase-auth-providers`)
   - OIDC (Red Hat Backstage Keycloak)
   - Microsoft OAuth2
   - GitHub authentication
   - LDAP (Active Directory)

4. **Plugin Tests** (`playwright/e2e/plugins/`)
   - RBAC (Role-Based Access Control)
   - Kubernetes actions
   - Notifications
   - Topology
   - Quay integration
   - Tekton
   - Dynamic plugins info
   - Adoption insights
   - Analytics

5. **Configuration Tests** (`playwright/e2e/configuration-test/`)
   - Config map validation
   - Environment-specific configurations

6. **Audit Log Tests** (`playwright/e2e/audit-log/`)
   - Audit logging functionality
   - Compliance verification

7. **Localization Tests** (`playwright/e2e/localization/`)
   - Verify UI displays correctly translated strings
   - Supports **German (de)**, **Spanish (es)**, **French (fr)**, **Italian (it)**, and **Japanese (ja)**
   - Runs in a dedicated `e2e-ocp-helm-localization-nightly` nightly job
   - Uses `showcase-localization-de`, `showcase-localization-es`, `showcase-localization-fr`, `showcase-localization-it`, `showcase-localization-ja` Playwright projects
   - Translation files located in `translations/` directory
   - Test helper: `e2e-tests/playwright/e2e/localization/locale.ts`

### Test Execution

#### CI/CD Pipeline Execution

In the CI/CD pipeline, tests are executed directly using Playwright's `--project` flag via `testing::run_tests()` in `.ci/pipelines/lib/testing.sh`:

```bash
yarn playwright test --project="${playwright_project}"
```

The namespace and Playwright project are decoupled, allowing flexible reuse. The `testing::check_and_test()` and `testing::run_tests()` functions accept an explicit `playwright_project` argument:

```bash
# Function signatures:
testing::check_and_test "${RELEASE_NAME}" "${NAMESPACE}" "${PLAYWRIGHT_PROJECT}" "${URL}" [max_attempts] [wait_seconds]
testing::run_tests "${RELEASE_NAME}" "${NAMESPACE}" "${PLAYWRIGHT_PROJECT}" "${URL}"
```

#### Local Development Scripts

The package aliases below require an environment already prepared by CI. For local tests,
run the equivalent project through `local-test.sh` so Bitwarden secrets and certificate files
are prepared correctly:

```bash
cd e2e-tests
BW_SESSION="$(env -u BW_CLEANEXIT bw unlock --raw)" && export BW_SESSION
BASE_URL=https://deployed-rhdh.example.com NAME_SPACE=showcase ./local-test.sh -- --project=showcase --headed
```

Set `NAME_SPACE_RBAC` for RBAC projects and `NAME_SPACE_RUNTIME` for the runtime project to the
corresponding deployed namespace. Caller-supplied namespaces and cluster connection values
are preserved. Host and container runs both download the current public AWS RDS CA bundle;
a failed download never falls back to a stored bundle.

Secret names, both Bitwarden profiles, recovery from failed checks, and creating or rotating
secrets are documented in `docs/e2e-tests/managing-e2e-secrets.md`; generic CLI usage lives in the
[upstream Secrets API](https://redhat-developer.github.io/rhdh-e2e-test-utils/api/secrets.html).
Read that guide before changing a local runner or adding a secret.

Package aliases for CI or an already prepared environment:

```bash
# Showcase tests - OpenShift deployments (Helm)
yarn showcase                       # General showcase tests
yarn showcase-rbac                 # General showcase tests with RBAC

# Showcase tests - Kubernetes deployments
yarn showcase-k8s                  # Kubernetes showcase tests
yarn showcase-rbac-k8s             # Kubernetes showcase tests with RBAC

# Showcase tests - Operator deployments
yarn showcase-operator             # Operator showcase tests
yarn showcase-operator-rbac        # Operator showcase tests with RBAC

# Showcase tests - Other scenarios
yarn showcase-runtime              # Runtime configuration tests
yarn showcase-upgrade              # Upgrade scenario tests

# Authentication provider tests
yarn showcase-auth-providers       # Auth provider tests

# Plugin tests
yarn showcase-sanity-plugins       # Plugin sanity tests

# Localization tests
yarn showcase-localization-de      # German localization tests
yarn showcase-localization-es      # Spanish localization tests
yarn showcase-localization-fr      # French localization tests
yarn showcase-localization-it      # Italian localization tests
yarn showcase-localization-ja      # Japanese localization tests

# Utility scripts
yarn lint                          # Oxlint checking
yarn lint:fix                      # Oxlint fixing
yarn fmt:check                     # Oxfmt checking
yarn fmt                           # Oxfmt fixing
yarn test:unit                     # Vitest unit and runner regression tests
yarn shellcheck                    # Shell script checking
```

Unit tests live under `e2e-tests/unit/` and use Vitest imports. Playwright specs use
the coverage-instrumented imports described in `e2e-coverage-imports`. Run unit tests
for changes to the local runners, stream decoder, and shared test utilities without
requiring a deployment. Run the relevant Playwright project for live E2E verification.
The current workspace has no `tsc:check` script; do not report a separate TypeScript
compilation check unless one was actually run.

**Note**: The CI pipeline no longer uses yarn script aliases. Instead, it runs Playwright directly with `yarn playwright test --project=<project-name>`. This decouples the namespace from the test project name, enabling more flexible namespace and test project reuse.

### Environment Variables

All the important environment variables are sourced in `.ci/pipelines/env_variables.sh`
CI secrets are mounted by OpenShift CI; local runners select equivalent names from Bitwarden.

⚠️ Important Notice
Do not persist local test secrets in `.env` files.
Store local credentials in the approved Bitwarden collection and CI secrets in the configured
OpenShift CI secret store. Local wrappers transport profile-selected values through FD 3,
materialize private files where needed, and load secrets into the test child environment.

CI retains the explicit `/tmp/secrets/<field>` reads and aliases in `env_variables.sh`.
The local container decodes its stream into a private tmpfs at that same path, so it
uses the original CI sourcing. Normalize both Azure certificate spellings to
`azure-db-certificates.pem` and reject conflicting aliases before writing files.

Host tests use `e2e-tests/local-test-secrets.ts` with the installed package's stream
decoder and child-process runner, without sourcing CI setup. Caller connection values
and namespaces are preserved; profile-supplied process controls and cluster-admin
credentials are excluded. The cluster-login helper reads only its two explicit fields
from the separate ephemeral-cluster profile.

Keep runtime secret files outside `SHARED_DIR` (flat cross-step state) and `ARTIFACT_DIR`
(public artifacts). The host adapter removes its private certificate directory after the
test process exits; container secrets retain their tmpfs lifecycle. Keep tracing disabled for secret-bearing
commands, and keep secret values out of process arguments and container environment flags. Store each GSM credential as a separate raw field for Prow censoring, as documented
in [OpenShift CI secret protection guidance](https://docs.ci.openshift.org/how-tos/adding-a-new-secret-to-ci-gsm/#protecting-secrets-from-leaking).

### Test Configuration

Playwright configuration (`e2e-tests/playwright.config.ts`):
- **Timeout**: 90 seconds global, 10-15 seconds for actions
- **Retries**: 2 on CI, 0 locally
- **Workers**: 3 on CI; Playwright's default locally, with project-specific overrides
- **Viewport**: 1920x1080
- **Video**: Retain on failure
- **Screenshots**: Enabled for all tests
- **Trace**: Retain on failure

### Key Differences: showcase-auth-providers vs Other Showcase Projects

The `showcase-auth-providers` project has several significant differences from other showcase projects, particularly in deployment and configuration:

#### **Namespace and Release Management**
- **Other Showcase Projects**: Use standard namespace patterns (`showcase-ci-nightly`, `showcase-rbac-nightly`)
- **showcase-auth-providers**: Uses dedicated namespace `showcase-auth-providers` and release `rhdh-auth-providers`
- **Logging**: Dedicated logs folder: `e2e-tests/auth-providers-logs`

#### **Test Retry Configuration**
- **Other Showcase Projects**: Typically use 2 retries (CI default)
- **showcase-auth-providers**: Configured with only 1 retry due to the complexity of authentication provider setup and teardown

#### **Configuration and Deployment Approach**
- **Other Showcase Projects**: Use Bash scripts for configuration and deployment
- **showcase-auth-providers**: Uses TypeScript for configuration and deployment management
- **Configuration Files**: Uses different configuration files compared to other showcase projects:
  - `e2e-tests/playwright/e2e/auth-providers/` directory structure with TypeScript test files
  - Dedicated values file: `.ci/pipelines/value_files/values_showcase-auth-providers.yaml`
  - TypeScript-based test configuration instead of Bash scripts
  - Dynamic RHDH instance management (create, update, restart, delete)

#### **Required Plugins and Dependencies**
- **Other Showcase Projects**: Standard plugin dependencies
- **showcase-auth-providers**: Requires specific plugins exported to `dynamic-plugins-root`:
  - `backstage-community-plugin-catalog-backend-module-keycloak-dynamic`
  - `backstage-plugin-catalog-backend-module-github-org-dynamic`
  - `backstage-plugin-catalog-backend-module-msgraph-dynamic`
  - `backstage-community-plugin-rbac`

#### **Authentication Provider Coverage**
- **Other Showcase Projects**: Standard authentication testing
- **showcase-auth-providers**: Tests multiple authentication providers:
  - OIDC using Red Hat Backstage Keycloak (RHBK)
  - Microsoft OAuth2 provider
  - GitHub authentication
  - LDAP using Active Directory (commented out)

#### **Test Structure and Files**
- **Other Showcase Projects**: Standard test file patterns
- **showcase-auth-providers**: Dedicated test structure:
  - `e2e-tests/playwright/e2e/auth-providers/` directory
  - Individual test files: `oidc.spec.ts`, `microsoft.spec.ts`, `github.spec.ts`, `ldap.spec.ts`
  - Tests verify: supported resolvers, user/group ingestion, nested groups, session token configuration

These differences make `showcase-auth-providers` a specialized testing environment focused on validating authentication provider integrations rather than general RHDH functionality testing.

## CI/CD Infrastructure

### OpenShift CI Overview

The RHDH CI/CD pipeline uses **OpenShift CI** with **Prow-based** automation and **ephemeral clusters** for testing.

Check the readme at `.ci/pipelines/README.md`

#### Key Components

1. **Ephemeral Clusters**: AWS-based clusters in `us-east-2` region
2. **Cluster Management**: Managed via cluster claims
3. **CI Job Types**: OCP, EKS, GKE, AKS environments
4. **Authentication**: Keycloak as default provider
5. **Secrets Management**: OpenShift CI mounted secrets; Bitwarden for local runs

### Cluster Pools

RHDH uses dedicated Hive cluster pools with the `rhdh` prefix on AWS `us-east-2`. Pool versions rotate as new OCP releases come out. Find the current list by filtering for `rhdh` in the [existing cluster pools](https://docs.ci.openshift.org/how-tos/cluster-claim/#existing-cluster-pools) page. See also `.ci/pipelines/README.md`.

### CI Job Types

#### Pull Request Tests
- **Trigger**: Automatic for code changes, manual with `/ok-to-test`
- **Environment**: Ephemeral OpenShift cluster
- **Scope**: Both RBAC and non-RBAC namespaces
- **Artifacts**: 6-month retention period

#### Nightly Tests
- **Schedule**: Automated nightly runs
- **Environments**: Multiple OCP versions, AKS, GKE
- **Reporting**: Slack notifications to `#rhdh-e2e-alerts`

### Test Execution Environment

#### Local Development
Host tests run through `local-test.sh` using the Node.js and Yarn versions declared
in `e2e-tests/package.json`. Container deployment and test runs use `local-run.sh`.

#### CI/CD Pipeline Execution
For CI/CD pipeline execution, tests run in a containerized environment using the image `.ci/images/Dockerfile`. This image is based on `mcr.microsoft.com/playwright` and uses Ubuntu as the base operating system.

**Note**: Any additional system dependencies required for testing must be installed in this Docker image to ensure CI/CD pipeline compatibility.

#### Alternative Execution Methods
**Podman Usage**: If you need to prepare the environment or run tests close to how CI/CD pipeline runs them, you can use Podman to run the `.ci/pipelines/openshift-ci-tests.sh` script inside the Docker image.

**RHEL/Fedora Systems**: On Playwright unsupported systems such as RHEL or Fedora, running tests inside the containerized environment using Podman is the recommended approach to avoid compatibility issues.

### Key CI Scripts

#### Main Orchestration
- **`.ci/pipelines/openshift-ci-tests.sh`**: Main test orchestration script
- **`.ci/pipelines/utils.sh`**: Utility functions
- **`.ci/pipelines/reporting.sh`**: Reporting and notifications
- **`.ci/pipelines/env_variables.sh`**: Environment variable management
- **`.ci/pipelines/playwright-projects.sh`**: Loads Playwright project names from `projects.json` as `$PW_PROJECT_*` variables

#### CI Infrastructure Package Configuration

The `.ci/package.json` file defines the CI infrastructure package configuration and development tools:

**Available Scripts:**
```bash
# Code quality and linting
yarn shellcheck              # Shell script linting with severity warnings
yarn prettier:check          # Check formatting for shell, markdown, and YAML files
yarn prettier:fix            # Fix formatting for shell, markdown, and YAML files
```

⚠️ **Important**: Before using any of these scripts, you must first run `yarn install` in the `.ci` folder to install the required dependencies (prettier, prettier-plugin-sh, shellcheck).

**Purpose**: This package provides essential tooling for maintaining code quality in the CI infrastructure, ensuring consistent formatting and shell script best practices across the pipeline scripts.

#### Shell Script Conventions

**Shell scripts in `.ci/` folder:**
- **Never use** `set pipefail` or `set -o pipefail`
- Only `.ci/pipelines/openshift-ci-tests.sh` defines global `set` options; other scripts inherit them
- Functions may temporarily disable/re-enable error handling with `set +e` / `set -e` pattern

#### Job Handlers
The main script dispatches to job-specific handlers in `.ci/pipelines/jobs/`:
- `handle_aks_helm` / `handle_aks_operator`: AKS Helm/Operator deployment
- `handle_eks_helm` / `handle_eks_operator`: EKS Helm/Operator deployment
- `handle_gke_helm` / `handle_gke_operator`: GKE Helm/Operator deployment
- `handle_ocp_nightly`: OCP Helm nightly tests (also handles OSD-GCP Helm)
- `handle_ocp_localization`: OCP Helm localization nightly tests
- `handle_ocp_operator`: OCP Operator nightly tests (also handles OSD-GCP Operator)
- `handle_ocp_pull`: OCP PR checks
- `handle_auth_providers`: Auth provider tests
- `handle_ocp_helm_upgrade`: Upgrade scenario tests

#### Special Case: showcase-auth-providers Deployment

The `showcase-auth-providers` project has a unique deployment workflow that differs significantly from other showcase projects:

**Handler**: `handle_auth_providers()` function in `.ci/pipelines/jobs/auth-providers.sh`
**Configuration**: Uses dedicated values file `values_showcase-auth-providers.yaml` with auth provider-specific settings
**Test Execution**: Runs TypeScript-based tests from `e2e-tests/playwright/e2e/auth-providers/` directory

### Access and Debugging

#### Cluster Access
For cluster pool admins, use the login script:
```bash
.ci/pipelines/ocp-cluster-claim-login.sh
```

It validates the Prow URL and resolves the cluster claim before loading Bitwarden
credentials. Use `--no-console` for login only or `--open-console` to request the
console explicitly. Non-interactive stdin skips the console prompt.

#### Debugging Process
1. Run the login script
2. Provide Prow log URL when prompted
3. Script resolves the claim, loads credentials, and logs in; console access is optional
4. Ephemeral clusters are deleted after CI job termination

### CI Configuration Files

- **Job Definitions**: [OpenShift Release Jobs](https://github.com/openshift/release/tree/master/ci-operator/jobs/redhat-developer/rhdh)
- **Configuration**: [OpenShift Release Config](https://github.com/openshift/release/tree/master/ci-operator/config/redhat-developer/rhdh)
- **Step Registry**: [OpenShift Release Steps](https://github.com/openshift/release/tree/master/ci-operator/step-registry/redhat-developer/rhdh)

### Debugging

#### Local Debugging
```bash
# Set local development flags
export ISRUNNINGLOCAL=true
export ISRUNNINGLOCALDEBUG=true

# Run tests locally
./local-test.sh -- --project=showcase-auth-providers --workers=1
```

#### CI Debugging
1. **Access Logs**: Check PR artifacts or CI logs
2. **Cluster Access**: Use cluster claim login script
3. **Environment Variables**: Verify required variables
4. **Test Failures**: Review test reports and screenshots

#### Common Debugging Tools
- **Playwright Inspector**: `./local-test.sh -- --project=PROJECT --debug`
- **Trace analysis**: `npx playwright trace open "test-results/${TEST_PATH}/trace.zip"`, then `npx playwright trace errors` or `npx playwright trace actions`; finish with `npx playwright trace close`
- **Screenshots**: Automatic on failure
- **Video Recording**: Available for all tests

## Key Dependencies and Common Issues

### System Dependencies

#### macOS Requirements
**Important**: macOS users need to use GNU `grep` and GNU `sed` instead of the built-in BSD versions to avoid compatibility issues with scripts and CI/CD pipelines.

Install using Homebrew:
```bash
brew install grep
brew install gnu-sed
```

**Important**: Make sure to set the GNU versions as default to ensure they are used instead of the built-in macOS versions.

**Note**: The built-in macOS versions of these tools may cause issues when running scripts or tests that expect GNU-compatible behavior.

### External Services

#### Required Services
- **GitHub**: Authentication, repository access
- **Keycloak**: Default authentication provider
- **OpenShift**: Primary deployment platform
- **Advanced Cluster Management**: For OCM plugins

### Internal Components

#### Core Components
- **Backstage**: Main application framework
- **Dynamic Plugins**: Plugin management system
- **Catalog**: Entity management
- **Scaffolder**: Template system

### Common Issues and Solutions

#### Test Failures
1. **Environment Issues**: Verify environment variables
2. **Authentication Problems**: Check credentials and tokens
3. **Resource Constraints**: Check cluster resources

#### CI Failures
1. **Cluster Issues**: Verify cluster availability
2. **Resource Limits**: Check resource quotas
3. **Network Problems**: Verify connectivity
4. **Configuration Errors**: Review job configuration

#### Plugin Issues
1. **Loading Failures**: Check plugin configuration
2. **Dependency Conflicts**: Verify package versions
3. **Configuration Errors**: Review plugin config
4. **Build Issues**: Check build process

## Documentation References

### Core Documentation
- [E2E Testing CI Documentation](docs/e2e-tests/CI.md)
- [Dynamic Plugins Documentation](docs/dynamic-plugins/index.md)
- [Authentication Providers README](e2e-tests/playwright/e2e/auth-providers/README.md)
- [OpenShift CI Pipeline README](.ci/pipelines/README.md)

### Configuration Files
- [Playwright Project Names (Single Source of Truth)](e2e-tests/playwright/projects.json)
- [Playwright Configuration](e2e-tests/playwright.config.ts)
- [Package Configuration](e2e-tests/package.json)
- [CI Test Script](.ci/pipelines/openshift-ci-tests.sh)

### External Resources
- [OpenShift CI Documentation](https://docs.ci.openshift.org/)
- [Playwright Documentation](https://playwright.dev/)
- [Red Hat Developer Hub Documentation](https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/main/)
- [Backstage Documentation](https://backstage.io/docs)
- [Dynamic Plugins Guide](https://github.com/backstage/backstage/tree/master/packages/backend-dynamic-feature-service)

### Key Scripts and Tools
- [Cluster Login Script](.ci/pipelines/ocp-cluster-claim-login.sh)
- [Test Reporting Script](.ci/pipelines/reporting.sh)
- [Environment Variables](.ci/pipelines/env_variables.sh)
- [Dynamic Plugin Installer](https://github.com/redhat-developer/rhdh-plugins/tree/main/workspaces/install-dynamic-plugins)

## Test Configuration Files (Config Maps)

### Overview

The RHDH e2e testing infrastructure uses two main configuration files located in `.ci/pipelines/resources/config_map/`:

1. **`app-config-rhdh.yaml`** - Non-RBAC configuration
2. **`app-config-rhdh-rbac.yaml`** - RBAC-enabled configuration

### Config Map Usage Pattern

The choice of config map depends on the **Playwright test project** being executed, as defined in `e2e-tests/playwright.config.ts`:

#### **app-config-rhdh.yaml** (Non-RBAC Configuration)

**Used for test projects that exclude RBAC testing:**

- `smoke-test` - Basic smoke tests
- `showcase` - General functionality tests (explicitly excludes RBAC tests)
- `showcase-k8s` - Kubernetes integration tests (explicitly excludes RBAC tests)
- `showcase-operator` - Operator-based tests (explicitly excludes RBAC tests)
- `showcase-runtime` - Runtime environment tests
- `showcase-sanity-plugins` - Plugin sanity tests
- `showcase-upgrade` - Upgrade scenario tests
- `showcase-localization-de` - German localization tests
- `showcase-localization-es` - Spanish localization tests
- `showcase-localization-fr` - French localization tests
- `showcase-localization-it` - Italian localization tests
- `showcase-localization-ja` - Japanese localization tests
- `showcase-auth-providers` - Authentication provider tests (uses special deployment process)

#### **app-config-rhdh-rbac.yaml** (RBAC Configuration)

**Used for test projects that include RBAC testing:**

- `showcase-rbac` - RBAC-specific tests
- `showcase-rbac-k8s` - Kubernetes + RBAC tests
- `showcase-operator-rbac` - Operator + RBAC tests

### **CRITICAL RULE: Config Map Selection**

**When adding new tests:**

1. **Identify the test project scope:**
   - Will the new test/plugin be tested with RBAC? → Use `app-config-rhdh-rbac.yaml`
   - Will the new test/plugin be tested without RBAC? → Use `app-config-rhdh.yaml`

2. **Check the Playwright project configuration:**
   - Projects that exclude RBAC tests (using `testIgnore` for RBAC patterns) → Use `app-config-rhdh.yaml`
   - Projects that include RBAC tests (using `testMatch` for RBAC patterns) → Use `app-config-rhdh-rbac.yaml`

### **Special Cases**

1. **showcase-auth-providers**: Although it uses the non-RBAC config pattern, it has its own specialized deployment process with dedicated values file (`values_showcase-auth-providers.yaml`) and TypeScript-based configuration management.

### **Configuration Deployment Process**

The config maps are deployed as Kubernetes ConfigMaps during CI/CD pipeline execution and are mounted into the RHDH pods to provide runtime configuration. The pipeline selects the appropriate config map based on the test project being executed.