OCPBUGS-106125: Remove all Cypress references from the codebase

[shahsahil264]

Analysis / Root cause:

The Cypress CI job is being removed after the migration to Playwright. This PR completes the repository-side cleanup required by OCPBUGS-106125 and CONSOLE-5232.

Solution description:

• Removed Cypress integration-test directories, configurations, fixtures, support code, and runner scripts.
• Removed Cypress npm packages, Cucumber/Gherkin tooling, reporters, scripts, and lockfile entries.
• Removed Cypress ESLint plugins, rules, aliases, and stale configuration.
• Removed Cypress CI/build artifacts and obsolete builder tooling.
• Updated README, testing, internationalization, and editor configuration to use Playwright.
• Removed Cypress-specific comments and imports from application and test code.
• Removed the dedicated migrate-cypress skill and consolidated migration guidance into the existing Playwright E2E skill and migration context.

PR #17156 separately removes the OLM and Dev Console migration artifacts. Together, the PRs satisfy the complete Cypress removal acceptance criteria.

Acceptance criteria validation:

• Cypress packages and lockfile entries removed.
• Cypress configs and integration-test directories removed.
• Cypress scripts and CI entrypoints removed.
• Cypress ESLint plugin/configuration removed.
• Cypress documentation and editor references removed or migrated.
• No executable Cypress imports or references remain; intentional migration guidance remains in migration-context.md and Playwright skill documentation.
• Frontend build passed.
• Yarn immutable install passed.
• JSON and shell syntax checks passed.

Screenshots / screen recording:

N/A - infrastructure cleanup only.

Test setup:

No special setup required.

Related issues:

• OCPBUGS-106125
• CONSOLE-5232
• PR #17156 for OLM and Dev Console migration artifacts.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@shahsahil264: This pull request references CONSOLE-5232 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Analysis / Root cause:

The Cypress-to-Playwright E2E migration is complete. All remaining Cypress test infrastructure, dependencies, and documentation references need to be removed from the codebase. This PR depends on #16882 (CONSOLE-5234) which removes the CI entrypoint scripts.

Solution description:

Complete removal of all Cypress references from the codebase:

Test infrastructure removed (7 directories, ~430 files):

• frontend/packages/integration-tests/ — 15 .cy.ts files, cypress configs, support files (@console/cypress-integration-tests)
• frontend/packages/operator-lifecycle-manager/integration-tests/ — 9 .cy.ts files (@console/operator-lifecycle-manager-integration-tests)
• frontend/packages/dev-console/integration-tests/ — 49 .feature files, step definitions (@dev-console/integration-tests)
• frontend/packages/helm-plugin/integration-tests/ — 11 .feature files, step definitions (@helm-plugin/integration-tests)
• frontend/packages/knative-plugin/integration-tests/ — 31 .feature files, step definitions (@knative-plugin/integration-tests)
• frontend/packages/topology/integration-tests/ — support/page-objects only
• frontend/packages/container-security/integration-tests/ — single test fixture file (relocated to __tests__/)

Dependencies removed from frontend/package.json:

• cypress, cypress-axe, cypress-cucumber-preprocessor, cypress-jest-adapter, cypress-multi-reporters, @cypress/webpack-preprocessor, gherkin-lint
• mocha-junit-reporter, mochawesome, mochawesome-merge, mochawesome-report-generator (Cypress reporting only)
• 18 Cypress scripts, dependenciesMeta, workspace patterns for integration-tests

CI/build cleanup:

• test-frontend.sh — removed yarn run gherkin-lint
• Dockerfile — removed CYPRESS_INSTALL_BINARY=0
• Dockerfile.builder — removed Cypress system deps (libgtk, libgconf, etc.)

Documentation updated:

• README.md — replaced Cypress "Integration Tests" section with Playwright
• TESTING.md — updated to reference Playwright
• INTERNATIONALIZATION.md — updated testing references
• AGENTS.md — updated E2E tool and migration section
• .gitignore — removed Cypress artifact patterns

Broken imports fixed:

• Relocated bad-pods.ts test fixture from deleted container-security/integration-tests/ to __tests__/
• Updated 6 spec file imports
• Cleaned up stale integration-tests references from jest.config.ts and knip.ts

Screenshots / screen recording:

N/A — infrastructure cleanup, no UI impact.

Test setup:

No special setup required.

Test cases:

• yarn install — lockfile regenerates cleanly (verified)
• yarn test — 1786 passed, same as main branch (9 pre-existing failures, verified identical)
• grep -rn "cypress\|gherkin" --include="*.sh" --include="*.ts" --include="*.js" --include="*.md" — no project source references remain (only node_modules)
• No broken imports from deleted integration-tests/ directories

Browser conformance:

N/A — No UI changes.

Additional info:

This is part of the Cypress-to-Playwright migration effort:

• CONSOLE-5234: Remove Cypress job in CI (#16882)
• CONSOLE-5232: Remove Cypress references (this PR)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5854d9ca-f298-4734-930f-97a47a4e7b96

📥 Commits

Reviewing files that changed from the base of the PR and between 2058db7 and ab239de.

⛔ Files ignored due to path filters (1)

• frontend/yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (2)

• frontend/eslint.config.ts
• frontend/packages/eslint-plugin-console/package.json

💤 Files with no reviewable changes (2)

• frontend/packages/eslint-plugin-console/package.json
• frontend/eslint.config.ts

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The change replaces Cypress references with Playwright guidance and configuration, updates container-security test fixture paths, and removes the legacy builder image configuration, scripts, Dockerfile, and documentation.

Changes

Test tooling transition and builder cleanup

Layer / File(s)	Summary
Playwright test alignment AGENTS.md, INTERNATIONALIZATION.md, frontend/jest.config.ts, frontend/setup-tests.js, .gitignore, Dockerfile, frontend/eslint.config.ts, frontend/packages/eslint-plugin-console/package.json, frontend/packages/console-shared/src/utils/test-errors.ts	Testing guidance, comments, Jest exclusions, Docker settings, ignore rules, and ESLint configuration now reference Playwright or remove Cypress-specific settings.
Container-security fixture imports frontend/packages/container-security/src/components/__tests__/*	Container-security tests now import the local bad-pods fixture. The fixture uses corrected package-relative imports.
Legacy builder removal .ci-operator.yaml, Dockerfile.builder, builder-run.sh, push-builder.sh, README.md	The builder image configuration, Dockerfile, build and run scripts, and maintenance instructions are removed.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to ab239

No concrete merge-blocking issue remains from the available review evidence.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	No failure condition is introduced. The authoritative diff changes no Go or Ginkgo test files. The changed frontend tests use Jest describe/it, and their titles are static; the pull request only c…
Test Structure And Quality	✅ Passed	PASS — the custom check applies only to Ginkgo test code. The pull request changes no Go or Ginkgo files. Its changed tests are Jest/React TypeScript files; the test changes only relocate `fakeVulnFor…
Microshift Test Compatibility	✅ Passed	The check is not applicable. The reviewed diff changes no Go files and adds no Ginkgo test definitions such as It, Describe, Context, or When. Changes are limited to frontend TypeScript/JavaScript tes…
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The review-scoped diff adds no Ginkgo e2e tests and changes no Go files. The changed test files are TypeScript Jest unit tests; their changes only relocate imports and fixtures. No new multi-nod…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS: The reviewed diff contains no deployment manifests, operator/controller code, or scheduling changes. It removes CI builder configuration and scripts, updates test/documentation metadata, moves a…
Ote Binary Stdout Contract	✅ Passed	PASS: The authoritative pull-request diff changes no Go files and introduces no OTE binary, main/suite setup, or process-level stdout code. The changed paths contain frontend/configuration, documentat…
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS: The reviewed range adds no Ginkgo tests and changes no Go files. The changed test files are existing TypeScript/Jest tests; their changes only relocate the bad-pods fixture and update imports.…
No-Weak-Crypto	✅ Passed	PASS. The reviewed diff adds no MD5, SHA1, DES, 3DES, RC4, Blowfish, ECB, custom crypto, or secret-comparison logic. JavaScript/TypeScript changes contain no crypto APIs or weak-algorithm identifiers.…
Container-Privileges	✅ Passed	No explicit container-privilege failure is introduced. Added diff lines contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or equivalent settings. Dockerfile `U…
No-Sensitive-Data-In-Logs	✅ Passed	PASS: The pull-request diff introduces no new logging calls or output paths. The changed source only updates imports, test configuration, comments, and fixture paths; addTestError still stores messa…
Title check	✅ Passed	The title clearly identifies the primary change: removing remaining Cypress references. It includes the required Jira issue prefix.
Description check	✅ Passed	The description covers the root cause, solution, acceptance criteria, screenshots, test setup, and related issues. It is mostly complete, although it does not provide explicit browser-conformance resu…

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[shahsahil264]

/hold

[shahsahil264]

/pipeline required

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

[shahsahil264]

/pipeline required

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

[shahsahil264]

/test e2e-gcp-console
/test e2e-playwright

[shahsahil264]

/jira refresh

[openshift-ci-robot]

@shahsahil264: This pull request references Jira Issue OCPBUGS-123182, which is invalid:

• expected the bug to target either version "5.1.0." or "openshift-5.1.0.", but it targets "5.0.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-121974, which is invalid:

• expected the bug to target either version "5.1.0." or "openshift-5.1.0.", but it targets "5.0.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@shahsahil264: This pull request references Jira Issue OCPBUGS-123182, which is invalid:

• expected the bug to target either version "5.1.0." or "openshift-5.1.0.", but it targets "5.0.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-121974, which is invalid:

• expected the bug to target either version "5.1.0." or "openshift-5.1.0.", but it targets "5.0.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

The Cypress-to-Playwright E2E migration is complete. All Cypress test infrastructure, CI scripts, dependencies, and documentation references need to be removed from the codebase (CONSOLE-5232).

Solution description:

Complete removal of all Cypress references from the codebase:

CI scripts removed:

• test-prow-e2e.sh — Prow CI entrypoint for Cypress E2E
• test-prow-e2e-techpreview.sh — empty stub
• frontend/integration-tests/test-cypress.sh — Cypress test runner
• Cleaned up stale Cypress comments in test-prow-playwright-e2e.sh

Test infrastructure removed (7 directories, ~430 files):

• frontend/packages/integration-tests/ — 15 .cy.ts files, cypress configs, support files (@console/cypress-integration-tests)
• frontend/packages/operator-lifecycle-manager/integration-tests/ — 9 .cy.ts files (@console/operator-lifecycle-manager-integration-tests)
• frontend/packages/dev-console/integration-tests/ — 49 .feature files, step definitions (@dev-console/integration-tests)
• frontend/packages/helm-plugin/integration-tests/ — 11 .feature files, step definitions (@helm-plugin/integration-tests)
• frontend/packages/knative-plugin/integration-tests/ — 31 .feature files, step definitions (@knative-plugin/integration-tests)
• frontend/packages/topology/integration-tests/ — support/page-objects only
• frontend/packages/container-security/integration-tests/ — single test fixture file (relocated to __tests__/)

Dependencies removed from frontend/package.json:

• cypress, cypress-axe, cypress-cucumber-preprocessor, cypress-jest-adapter, cypress-multi-reporters, @cypress/webpack-preprocessor, gherkin-lint
• mocha-junit-reporter, mochawesome, mochawesome-merge, mochawesome-report-generator (Cypress reporting only)
• 18 Cypress scripts, dependenciesMeta, workspace patterns for integration-tests

CI/build cleanup:

• test-frontend.sh — removed yarn run gherkin-lint
• Dockerfile — removed CYPRESS_INSTALL_BINARY=0
• Dockerfile.builder — removed Cypress system deps (libgtk, libgconf, etc.)

Documentation updated:

• README.md — replaced Cypress "Integration Tests" section with Playwright
• TESTING.md — updated to reference Playwright
• INTERNATIONALIZATION.md — updated testing references
• AGENTS.md — updated E2E tool and migration section
• .gitignore — removed Cypress artifact patterns

Broken imports fixed:

• Relocated bad-pods.ts test fixture from deleted container-security/integration-tests/ to __tests__/
• Updated 6 spec file imports
• Cleaned up stale integration-tests references from jest.config.ts and knip.ts

Note: The corresponding CI job definitions in openshift/release (removing e2e-gcp-console and promoting e2e-playwright) will be handled in a separate PR to that repo under CONSOLE-5234.

Screenshots / screen recording:

N/A — infrastructure cleanup, no UI impact.

Test setup:

No special setup required.

Test cases:

• yarn install — lockfile regenerates cleanly (verified)
• yarn test — 1786 passed, same as main branch (9 pre-existing failures, verified identical)
• grep -rn "cypress\|gherkin" --include="*.sh" --include="*.ts" --include="*.js" --include="*.md" — no project source references remain (only node_modules)
• No broken imports from deleted integration-tests/ directories
• test-prow-playwright-e2e.sh and test-playwright-e2e.sh unchanged and functional

Browser conformance:

N/A — No UI changes.

Additional info:

Related JIRAs:

• CONSOLE-5232: Remove Cypress references (this PR)
• CONSOLE-5234: Remove Cypress CI job definitions from openshift/release (separate PR)

Summary by CodeRabbit

• Testing

• End-to-end testing is now documented and configured around Playwright.

• Legacy Cypress, Cucumber, Gherkin, reporting workflows, and related test fixtures were removed.

• Playwright commands support full, smoke, console, headed, debug, and UI test modes.

• Integration test guidance covers Core Console, OLM, Developer Console, Helm, Knative, Topology, Web Terminal, and internationalization.

• Documentation

• README and testing documentation now include Playwright setup, required environment variables, and CI execution guidance.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@shahsahil264: This pull request references Jira Issue OCPBUGS-106125, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

The Cypress-to-Playwright E2E migration is complete. All Cypress test infrastructure, CI scripts, dependencies, and documentation references need to be removed from the codebase (CONSOLE-5232).

Solution description:

Complete removal of all Cypress references from the codebase:

CI scripts removed:

• test-prow-e2e.sh — Prow CI entrypoint for Cypress E2E
• test-prow-e2e-techpreview.sh — empty stub
• frontend/integration-tests/test-cypress.sh — Cypress test runner
• Cleaned up stale Cypress comments in test-prow-playwright-e2e.sh

Test infrastructure removed (7 directories, ~430 files):

• frontend/packages/integration-tests/ — 15 .cy.ts files, cypress configs, support files (@console/cypress-integration-tests)
• frontend/packages/operator-lifecycle-manager/integration-tests/ — 9 .cy.ts files (@console/operator-lifecycle-manager-integration-tests)
• frontend/packages/dev-console/integration-tests/ — 49 .feature files, step definitions (@dev-console/integration-tests)
• frontend/packages/helm-plugin/integration-tests/ — 11 .feature files, step definitions (@helm-plugin/integration-tests)
• frontend/packages/knative-plugin/integration-tests/ — 31 .feature files, step definitions (@knative-plugin/integration-tests)
• frontend/packages/topology/integration-tests/ — support/page-objects only
• frontend/packages/container-security/integration-tests/ — single test fixture file (relocated to __tests__/)

Dependencies removed from frontend/package.json:

• cypress, cypress-axe, cypress-cucumber-preprocessor, cypress-jest-adapter, cypress-multi-reporters, @cypress/webpack-preprocessor, gherkin-lint
• mocha-junit-reporter, mochawesome, mochawesome-merge, mochawesome-report-generator (Cypress reporting only)
• 18 Cypress scripts, dependenciesMeta, workspace patterns for integration-tests

CI/build cleanup:

• test-frontend.sh — removed yarn run gherkin-lint
• Dockerfile — removed CYPRESS_INSTALL_BINARY=0
• Dockerfile.builder — removed Cypress system deps (libgtk, libgconf, etc.)

Documentation updated:

• README.md — replaced Cypress "Integration Tests" section with Playwright
• TESTING.md — updated to reference Playwright
• INTERNATIONALIZATION.md — updated testing references
• AGENTS.md — updated E2E tool and migration section
• .gitignore — removed Cypress artifact patterns

Broken imports fixed:

• Relocated bad-pods.ts test fixture from deleted container-security/integration-tests/ to __tests__/
• Updated 6 spec file imports
• Cleaned up stale integration-tests references from jest.config.ts and knip.ts

Note: The corresponding CI job definitions in openshift/release (removing e2e-gcp-console and promoting e2e-playwright) will be handled in a separate PR to that repo under CONSOLE-5234.

Screenshots / screen recording:

N/A — infrastructure cleanup, no UI impact.

Test setup:

No special setup required.

Test cases:

• yarn install — lockfile regenerates cleanly (verified)
• yarn test — 1786 passed, same as main branch (9 pre-existing failures, verified identical)
• grep -rn "cypress\|gherkin" --include="*.sh" --include="*.ts" --include="*.js" --include="*.md" — no project source references remain (only node_modules)
• No broken imports from deleted integration-tests/ directories
• test-prow-playwright-e2e.sh and test-playwright-e2e.sh unchanged and functional

Browser conformance:

N/A — No UI changes.

Additional info:

Related JIRAs:

• CONSOLE-5232: Remove Cypress references (this PR)
• CONSOLE-5234: Remove Cypress CI job definitions from openshift/release (separate PR)

Summary by CodeRabbit

• Testing

• End-to-end testing is now documented and configured around Playwright.

• Legacy Cypress, Cucumber, Gherkin, reporting workflows, and related test fixtures were removed.

• Playwright commands support full, smoke, console, headed, debug, and UI test modes.

• Integration test guidance covers Core Console, OLM, Developer Console, Helm, Knative, Topology, Web Terminal, and internationalization.

• Documentation

• README and testing documentation now include Playwright setup, required environment variables, and CI execution guidance.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[shahsahil264]

Addressed the builder cleanup review. Removed:

• Dockerfile.builder
• .ci-operator.yaml
• Obsolete push-builder.sh and builder-run.sh helpers
• README instructions for updating the retired tectonic-console-builder image

The only remaining Dockerfile.builder reference is unrelated fixture data for an external Gitea repository.

[shahsahil264]

Addressed the ESLint review. Removed the Cypress ESLint overlay from frontend/eslint.config.ts, removed eslint-plugin-cypress from frontend/packages/eslint-plugin-console/package.json, and regenerated frontend/yarn.lock. No Cypress ESLint config references remain.

[shahsahil264]

/pipeline-required
/test e2e-cypress
/test e2e-gcp-console
/test e2e-gcp-console-techpreview

[shahsahil264]

/test e2e-gcp-console
/test e2e-gcp-console-techpreview

[shahsahil264]

/retest

[shahsahil264]

/test e2e-gcp-console
/test e2e-gcp-console-techpreview

[shahsahil264]

/test e2e-gcp-console
/test e2e-gcp-console-techpreview

[shahsahil264]

/test e2e-gcp-console

[openshift-ci]

@shahsahil264: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-playwright-techpreview	efda5e0	link	false	/test e2e-playwright-techpreview
ci/prow/e2e-playwright	efda5e0	link	false	/test e2e-playwright
ci/prow/e2e-cypress	cee3373	link	false	/test e2e-cypress
ci/prow/e2e-gcp-console	869c3c2	link	true	/test e2e-gcp-console

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.