What problem does it solve?
Writing Playwright e2e tests for Positron requires following project-specific conventions (custom fixtures, suite IDs, tags, page objects) that are easy to get wrong, leading to flaky, broken, or unmaintainable tests.
Core Features & Use Cases
- Test Authoring Guidance: Enforces the mandatory test file structure, including imports from
../_test.setup, suiteId: __filename, and platform/feature tags.
- Fixture and Page Object Reference: Documents worker-scoped and test-scoped fixtures (
app, python, r, sessions, hotKeys, settings) and the app.workbench.* page object model.
- Flake Prevention: Catalogs common mistakes such as fixed waits, wrong retry mechanisms, missing cleanup, and hardcoded interpreter versions.
- Use Case: When adding a new regression test for the Data Explorer, use this Skill to copy the correct file structure, pick the right fixtures and tags, and write assertions that follow Positron's retry and selector conventions.
Quick Start
Write a new Playwright e2e test for the Positron console feature following the project's test conventions.