Automate regression testing for top feature: Universal Visual Editor (UVE) (3/3)

Parent Issue

Related to #30781

Task

To safeguard the stability and functionality of the Universal Visual Editor (UVE) in dotCMS, regression testing for this feature must be automated. This is the third of the top three features identified for automation, based on telemetry, QA feedback, and stakeholder priorities. Automating these test cases will enhance efficiency, reduce manual efforts, and ensure consistent validation of critical UVE functionalities during every release.

Tasks:

Review Test Cases:

• Analyze the test cases provided by the QA department for the UVE.
• Ensure the cases cover essential workflows, edge cases, and complex user scenarios related to UVE functionalities.

Script Test Cases:

• Write automated test scripts for UVE workflows using the approved automation framework (e.g., Playwright, Selenium).
• Include tests for key UVE features, such as:
  - Content editing
  - Drag-and-drop functionality
  - Layout adjustments
  - Multi-language support
  - Previewing changes in real-time

Integrate Tests:

• Incorporate the test scripts into the regression suite.
• Set up the CI/CD pipeline to execute these tests automatically during build and release processes.

Validate and Monitor:

• Execute the automated scripts to verify functionality and ensure no regressions.

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

Acceptance Criteria

• All test cases for UVE provided by the QA department are successfully automated.
• The scripts cover critical and high-traffic UVE workflows, ensuring comprehensive validation.
• Tests are integrated into the CI/CD pipeline and run without failures during builds.

Start with the QA department's UVE test cases and identify the existing regression suite and CI/CD pipeline entry points. Confirm whether Playwright or Selenium is approved, then map coverage for content editing, drag-and-drop, layouts, languages, and previewing. Done means all supplied critical workflows are automated, integrated into builds and releases, and pass consistently.