Menú
Guidelines for naming test folders and namespaces following the Unit.[Component] convention.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Mandatory rule requiring a corresponding test file for every business logic file and UI component.
Catalog of all specialized skills used across the FinanzApp project (Frontend & Backend).
Guidelines for clean code, readability, and the "No Comments" policy.
Mandatory rule for EF Core migrations and database updates.
Mandatory rules for automatically updating README.md when creating files or tests.
Guidelines for cross-layer testing (Hooks + UI + Services) using real logic and MSW for network interception.
| name | test-naming-convention |
| description | Guidelines for naming test folders and namespaces following the Unit.[Component] convention. |
To maintain a clean and standardized test suite, all unit tests must follow a specific directory and namespace structure.
Test subdirectories within the Tests/ project must use the Unit. prefix followed by the component name being tested.
Tests/Unit.Services/, Tests/Unit.Data/, Tests/Unit.ApiClient/Tests/Services/, Tests/Data/, Tests/Repositories/The namespace of each test file must mirror the folder structure exactly.
namespace Tests.Unit.[ComponentName];// File: Tests/Unit.Services/AuthServiceTests.cs
namespace Tests.Unit.Services;
[ClassName]Tests.csPersonaService.cs -> PersonaServiceTests.csThe structure inside Tests/Unit.[Category] should mirror the structure of the source project (e.g., matching subfolders for sub-namespaces).