Epic Goal

Enhance test coverage and maintainability for the OpenShift Pipelines Console Plugin by implementing a comprehensive E2E test suite for dynamic plugin scenarios.

Why is this important?

This work strengthens the plugin's reliability by adding automated end-to-end coverage specifically for dynamic plugin loading and integration scenarios. It significantly reduces regression risk during routine upgrades or OCP platform changes, ensuring the plugin loads, registers, and functions correctly within the live console environment.

Scenarios

• Automated E2E tests validate that the dynamic plugin loads, registers its extensions, and renders components as expected within the OCP console.

• Key user journeys are covered by the new E2E tests, including:
  • Overview: Validating the content and data on the main overview page.
  • Creation Flows: Testing all three pipeline creation flows.
  • Pipeline List Page: Verifying pipelines are listed correctly.
  • PipelineRun List Page: Checking the list of runs and validating the "Rerun" functionality.
  • Start Pipeline Run: Testing the flow to manually start a new PipelineRun.
  • PipelineRun Details Page: Navigating to the details of a running PipelineRun and testing the "Cancel" and "Stop" actions.
  • TaskRun Scenarios: Implementing similar list, details, and action validation for TaskRuns as present for Pipeline Runs.
  • Manual approval setup (optional)
  • Event listeners / Triggers / TriggerTemplate flow (optional)
  • PAC (optional but good to have)
• All CI pipelines pass with the new E2E test suite integrated and running successfully.

Acceptance Criteria (Mandatory)

• CI MUST be running successfully with all automated tests, including the new dynamic plugin E2E suite, passing.

• The new E2E test suite MUST cover the critical user journeys for the plugin.

• Documentation MUST be provided for running, debugging, and maintaining the new E2E tests.

Dependencies (internal and external)

• Internal:

• • Availability of the OpenShift Console's E2E testing framework.

• • A stable build of the Pipelines Console Plugin to test against.

• • Access to a running OCP cluster environment for CI test execution.

Previous Work (Optional)

• Existing E2E test framework setup for plugin validation (if any).

Done Checklist

• Acceptance criteria are met.

• User Journey automation is delivered for critical dynamic plugin scenarios.

• Support and SRE teams are provided with documentation and knowledge to analyze E2E test failures and support the test suite in production pipelines.