testing-frontend

Enforce Angular frontend testing standards for component and service unit tests.

Updated Aug 27, 2026

Search Tags:#testing #frontend #angular #unit test #component test #service test

Ready to run

npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill testing-frontend

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-frontend
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/testing-frontend
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill testing-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures the stability and reliability of the frontend application by enforcing comprehensive testing standards for components and services.

Core Features & Use Cases

Component Testing: Write deterministic tests for individual UI components.
Service Testing: Verify the logic and behavior of frontend services.
Use Case: When developing a new user authentication component, use this Skill to write unit tests that cover successful login, failed login, and edge cases like empty input fields.

Quick Start

Write a new test file for the UserProfile component following the established naming conventions.

Frequently Asked Questions about testing-frontend

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

FAQPage Schema

How do I write unit tests for Angular components and services?▼

Angular component and service unit tests are written by creating test files for TypeScript and HTML components within the `apps/web` directory. Tests must be deterministic, cover edge cases, and achieve a minimum of 70% code coverage for components.

What is the minimum code coverage required for Angular components in this workflow?▼

The minimum code coverage required for Angular components is 70%. This standard ensures UI stability by enforcing that all component and service unit tests cover edge cases and behave deterministically across the frontend application.

Do I need to follow specific file path rules for frontend testing?▼

Frontend testing rules apply specifically to all TypeScript and HTML files located within the `apps/web` directory. This ensures that component and service unit tests are correctly scoped to the Angular web application structure.

How do I test edge cases in an Angular user authentication component?▼

To test edge cases in an Angular authentication component, write unit tests that cover scenarios like empty input fields, failed logins, and successful logins. This approach ensures deterministic behavior and comprehensive edge case coverage for the UI component.

Why do my frontend component tests fail to ensure UI stability?▼

Frontend component tests fail to ensure UI stability when they are not deterministic, lack edge case coverage, or fall below the 70% code coverage threshold required for components in the `apps/web` directory.

Can I use this approach to test both TypeScript logic and HTML templates?▼

Yes, you can test both TypeScript logic and HTML templates because the testing standards apply to all TypeScript and HTML files within the `apps/web` directory, covering both component rendering and frontend service behavior.