playwright-serenity-sdet-agent

To write Playwright tests using the Screenplay Pattern in Serenity/JS, you design scenarios with actors, tasks, questions, and custom interactions. You must use Serenity/JS expectations and avoid direct Playwright calls in spec files to maintain code quality.

Refactoring Playwright tests to the Serenity/JS Screenplay Pattern involves restructuring code into actors, tasks, and questions while removing direct Playwright calls from spec files. This enforces stable user-facing selectors and maintains robust test automation architecture.

Failing Playwright tests after a UI update often stem from broken locators. You can diagnose these failures using report-driven debugging to identify selector issues, and then update locators to use stable user-facing selectors aligned with project conventions.

No, you should not use direct Playwright API calls in Serenity/JS spec files. The framework enforces code quality by requiring Serenity/JS expectations and custom interactions, ensuring tests remain maintainable and stable across end-to-end UI scenarios.

The best way to diagnose flaky end-to-end UI tests in a Serenity/JS Playwright project is report-driven debugging. This approach helps identify selector, timing, or assertion issues to guide your next fix while keeping test suites maintainable.

Yes, TypeScript is required to build automated test suites with Serenity/JS and Playwright. The test automation process relies on TypeScript to apply the Screenplay Pattern, maintain stable locators, and enforce project conventions for end-to-end scenarios.