Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-72722

Migrate Tier1, Tier2 and Gating tests to Playwright

XMLWordPrintable

    • Playwright Migration
    • Quality / Stability / Reliability
    • 77
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • Test Execution and Parallelism — Parallel execution with full isolation, eliminating sequential dependencies
      • Framework-to-Framework Test Matching — Coverage mapping between Cypress and Playwright with traceability via test IDs
      • Test Consolidation and Organization — Consolidation rules to optimize structure while maintaining coverage
      • Reporting and Traceability — Allure integration
      • Test Reliability and Stability — Remove flakiness with robust waiting strategies and error handling
      Show
      Test Execution and Parallelism — Parallel execution with full isolation, eliminating sequential dependencies Framework-to-Framework Test Matching — Coverage mapping between Cypress and Playwright with traceability via test IDs Test Consolidation and Organization — Consolidation rules to optimize structure while maintaining coverage Reporting and Traceability — Allure integration Test Reliability and Stability — Remove flakiness with robust waiting strategies and error handling
    • None
    • To Do
    • 100% To Do, 0% In Progress, 0% Done

      Goal

      Migrate end-to-end tests from Cypress to Playwright for the KubeVirt OpenShift plugin, enabling parallel test execution, improved test isolation, and enhanced maintainability. This migration provides QA engineers and developers with a modern, scalable test framework that supports faster feedback cycles and comprehensive test coverage across Gating, Tier1, and Tier2 test suites. The expected outcome is a fully migrated and consolidated test suite with 313+ tests running reliably in parallel, where Gating tests are complete, and Tier1/Tier2 tests are consolidated following best practices (combining navigation-only checks while keeping CRUD operations separate). Test results are to be captured with the Allure reporter.

      User Stories


      • As a Quality Engineer, I want to run Tier 1 tests in parallel with improved isolation, so that test execution is faster and more reliable, enabling quicker feedback on code changes and reducing flakiness from shared state dependencies.
      • As a Quality Engineer, I want to run Tier 2 tests in parallel with improved isolation, so that test execution is faster and more reliable, enabling quicker feedback on code changes and reducing flakiness from shared state dependencies.
      • As a Quality Engineer, I want to run Gating tests in parallel with improved isolation, so that test execution is faster and more reliable, enabling quicker feedback on code changes and reducing flakiness from shared state dependencies.
      • As a Quality Engineer engineer, I want Playwright test results to be captured in a format that could be used to generate Allure test reports.

      Notes

      • Shared resource dependencies → per-test VM creation with fixtures
      • Sequential test dependencies → self-contained tests with explicit setup
      • Architectural differences → layered architecture with type-safe context
      • Test flakiness → robust waiting strategies and improved locators
      • Test organization → Playwright-native grouping

              mschatzm@redhat.com Matan Schatzman
              rh-ee-bmaio Bruno Maio
              Bruno Maio
              Guohua Ouyang Guohua Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: