What problem does it solve? Angular test suites often pass while the real application is broken, because TestBed provides its own environment and masks bootstrap or provider errors. This Skill provides house conventions for writing Angular tests that assert observable behavior, route to the correct test runner, and avoid false-confidence patterns. ## Core Features & Use Cases - Runner routing: Detects whether the workspace uses Karma/Jasmine, Jest, or Vitest from angular.json or package.json, and applies the matching mocking and timing APIs without mixing them. - Strategy by role: Covers components, services with HttpTestingController, signal stores, pipes, directives, guards, signals, and routed components via RouterTestingHarness. - Suite auditing: Ships a references/suite-audit.md catalog of false-confidence anti-patterns (assertion-free, tautological, missing-await, swallowed-exception) plus StrykerJS mutation testing guidance. - Use Case: When adding a spec for a bug fix in a standalone OnPush component, load this Skill to wire inputs through componentRef.setInput, drive change detection explicitly, and name the spec for the defect it pins. ## Quick Start Load the angular-testing skill before writing or reviewing tests for my Angular standalone components and services.
