angular-playwright

Automate Angular end-to-end tests with Playwright narrative-driven specs.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/slusset/intention-driven-design --skill angular-playwright
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: angular-playwright
Source: https://github.com/slusset/intention-driven-design/tree/main/technical-skills/angular-playwright
Command: npx skills add https://github.com/slusset/intention-driven-design --skill angular-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Angular applications often require robust end-to-end tests that remain maintainable as the UI evolves. This Skill provides a structured approach to writing Playwright tests for Angular apps using a narrative-driven specs system (journeys, journey-maps, stories, features, fixtures) to ensure traceability and repeatability.

Core Features & Use Cases

  • Narrative-driven specs: follow journeys, journey maps, stories, features, and fixtures to organize tests and maintain alignment with intent.
  • Angular-focused reliability: enforce Angular-specific testing patterns, including stable reactive forms handling and data-test selectors.
  • Traceable testing workflow: integrate with specs/fixtures and journey sources to produce reproducible tests and clear headers for audits and reviews.

Quick Start

Run an end-to-end test for an Angular app following the narrative specs chain.

Frequently Asked Questions about angular-playwright

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Playwright e2e tests for an Angular application?

Apply a narrative-driven specs system of journeys, journey maps, stories, features, and fixtures to structure Playwright e2e tests for Angular, maintaining alignment with intent and ensuring traceability.

What is narrative-driven testing for Angular apps?

Narrative-driven testing organizes end-to-end tests into journeys, journey maps, and stories to verify navigation, visibility, and URLs while producing clear test headers for audits and reviews.

Do I need data-testid selectors to run Playwright tests on Angular?

Yes, narrative-driven Playwright tests require Angular projects configured with data-testid selectors, fixtures under specs/fixtures, and integration with journey map sources to verify navigation and visibility.

How do I maintain traceability in Angular end-to-end testing?

Maintain traceability in Angular e2e testing by integrating journey map sources with specs/fixtures to produce reproducible tests and generate clear test-header outputs for audits and reviews.

What's the best way to handle Angular reactive forms in Playwright e2e tests?

Handle Angular reactive forms in Playwright e2e tests by applying Angular-specific testing patterns that enforce stable selector usage and narrative-driven journey orchestration across features and fixtures.