prowler-test-ui

Write Playwright E2E tests for the Prowler UI under the ui/tests directory, leveraging reusable base pages and test helpers to standardize UI automation. This approach uses TypeScript and MCP-guided workflows to drive test consistency and reliable results.

Structure UI automation tests by referencing base page classes and test helpers, which provide standardized conventions for driving Playwright test consistency. These reusable patterns accelerate deterministic test exploration and reliable results.

Yes, you need TypeScript support configured in your project before running Prowler UI E2E tests. Ensure Playwright is also installed and properly set up to leverage the base page classes and helpers from this skill in your tests.

Yes, you can use reusable base pages and helpers to drive test consistency in Playwright. These components provide standardized conventions for UI automation, ensuring deterministic test exploration and reliable results across the Prowler UI.

MCP-guided workflows ensure deterministic test exploration and reliable results in UI E2E testing. They provide structured guidance when writing Playwright tests, helping developers navigate test scenarios consistently and avoid flaky test outcomes.

No, prowler-test-ui requires Playwright and TypeScript support configured in the project. It provides reusable base pages and helpers but needs these underlying frameworks to execute UI automation tests under the ui/tests directory.