test-architecture

Document a canonical test pyramid for Clean Architecture backend and frontend projects.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/JPerezC92/TisOps-Hub --skill test-architecture-jperezc92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-architecture
Source: https://github.com/JPerezC92/TisOps-Hub/tree/main/.claude/skills/test-architecture
Command: npx skills add https://github.com/JPerezC92/TisOps-Hub --skill test-architecture-jperezc92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference blueprint for structuring tests across backend and frontend projects using Clean Architecture to ensure consistent quality.

Core Features & Use Cases

  • Defines a canonical test pyramid: unit, integration, and E2E across backend and frontend.
  • Provides guidance on test placement, naming, and review practices to support auditing and improvement.
  • Includes practical patterns for common modules (e.g., controllers, use cases, services) and suggested tooling.

Quick Start

Open apps/reports-api and apps/web and map your current tests to the pyramid structure to begin aligning practice with the blueprint.

Frequently Asked Questions about test-architecture

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

FAQPage Schema
How do I structure a test pyramid for backend and frontend projects using Clean Architecture?

A test pyramid for Clean Architecture separates backend and frontend tests into unit, integration, and E2E layers. This blueprint defines canonical structures, file naming, and tooling to map tests across apps/reports-api and apps/web for consistent quality.

What is the canonical test pyramid structure for Clean Architecture?

The canonical test pyramid structure for Clean Architecture spans unit, integration, and E2E tests. It provides practical patterns for common modules like controllers, use cases, and services, guiding test writing, reviewing, and auditing.

How do I apply a test pyramid blueprint to existing frontend and backend apps?

Apply the test pyramid blueprint by mapping your current tests to the defined unit, integration, and E2E structure. Align existing tests for apps/reports-api and apps/web with the specified file naming and testing practices.

Does this test pyramid blueprint work with Vitest for frontend testing?

Yes, the test pyramid blueprint includes suggested tooling for frontend testing and can be applied alongside Vitest. It defines test placement and recommended patterns to structure your web application testing consistently.

What are the best practices for naming and placing E2E and integration tests?

Best practices for E2E and integration tests involve enforcing canonical file naming and specific test placement within the pyramid structure. This ensures tests are organized by layer and module to support reviewing and auditing.