rstudio-create-playwright-tests

To write stable Playwright tests for the RStudio UI, use stable selectors derived from source code, avoid dynamic IDs, and interact with the Ace editor using pressSequentially to ensure cross-environment compatibility.

Playwright UI tests fail with the Ace editor in RStudio when using standard typing methods. You must use pressSequentially for text input and forced clicks to handle the editor's custom event handling correctly.

The best way to execute commands in Playwright tests across RStudio Desktop and Server is using the .rs.api.executeCommand() method, which ensures cross-mode compatibility and prevents environment-specific test failures.

Yes, you can use Playwright to migrate existing UI tests for RStudio Desktop and Server environments by applying structured review checklists and standard patterns to ensure cross-platform stability.

To prevent flaky Playwright tests in RStudio, you should avoid using dynamic IDs. Instead, derive stable selectors from RStudio source code patterns to reliably locate UI elements across test runs.

Using TypeScript to structure your RStudio Playwright test suite is recommended to enforce type safety and maintainable test structures, consolidating rules and review workflows into a single reference.