Improve ELSA Studio Support for Playwright Automation Testing/ELSA Studio – Playwright Automation Testing Challenges

ELSA Studio – Playwright Automation Testing Challenges
During Playwright automation testing of ELSA Studio, we identified several technical limitations that impact test stability and reliability:

ELSA Studio is hosted inside a Blazor iframe, increasing locator complexity.
Drag-and-drop on the workflow designer canvas is unstable and causes intermittent failures.
Blazor WebAssembly load times are inconsistent, resulting in timing-related test failures.
Key UI elements do not expose stable data-testid attributes, making locators fragile.
Workflow canvas state is not preserved between test runs.
Blazor WebAssembly API calls cannot be reliably mocked for negative test scenarios.
ELSA version upgrades frequently require locator updates due to DOM changes.

These issues significantly affect the stability, maintainability, and scalability of the Playwright automation framework. Requesting guidance and possible improvements to make ELSA Studio more automation-friendly.

Start by reproducing the Playwright automation challenges in ELSA Studio, focusing on the Blazor iframe, workflow designer canvas, unstable loading, missing data-testid attributes, state preservation, and API mocking. Narrow the request to a defined improvement with acceptance criteria and tests demonstrating stable automation across the affected scenarios.

Written by the indexing model from the issue text.