Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

testing-vitest

Estrelas2

Forks0

Atualizado27 de fevereiro de 2026 às 11:26

Vitest testing patterns for LifeOS backend and frontend. Use when adding unit/integration tests, refactoring behavior, fixing regressions, or validating business rules such as ownership and spaced review scheduling.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

pvidaal07

pvidaal07/LifeOS

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	testing-vitest
description	Vitest testing patterns for LifeOS backend and frontend. Use when adding unit/integration tests, refactoring behavior, fixing regressions, or validating business rules such as ownership and spaced review scheduling.

Testing Vitest

Objetivo

Cubrir comportamiento de negocio con tests estables, rápidos y legibles.

REQUIRED

Escribir tests AAA (Arrange, Act, Assert).
Nombrar casos en lenguaje de negocio, no de implementación.
Priorizar unit tests para lógica pura (algoritmos, validaciones, mappers).
Añadir integration tests para flujos críticos de API/repositorio.
Mockear dependencias externas (DB real, red, tiempo) cuando no sea un test de integración.
Cubrir casos borde: ownership, estados inválidos, fechas límite, respuestas vacías.

NEVER

No testear detalles internos frágiles (spies excesivos, private methods).
No depender del orden global de ejecución.
No introducir sleeps reales si se puede usar fake timers.

Estructura sugerida

Backend: backend/test/{domain,application,integration}.
Frontend: tests junto a feature o en frontend/src/test por módulo.

Flujo recomendado

Reproducir bug/regla faltante en test.
Implementar cambio mínimo.
Ejecutar suite objetivo y luego suite completa.

Mais deste repositório

mesmo repositório

nestjs-best-practices

pvidaal07/LifeOS

NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.

2026-02-272

api-contracts

pvidaal07/LifeOS

API DTO and response contract rules for LifeOS backend/frontend compatibility. Use when adding or changing endpoints, request/response DTOs, error payloads, versioning decisions, or Swagger/OpenAPI documentation.

2026-02-272

auth-and-ownership

pvidaal07/LifeOS

Authentication and ownership enforcement rules for LifeOS multi-user isolation. Use when creating or changing auth flows, guarded endpoints, user-scoped queries, or nested resource access checks.

2026-02-272

clean-architecture-ddd

pvidaal07/LifeOS

Clean Architecture + DDD rules for this repo. Triggers: adding/refactoring code across src/domain|application|infrastructure, moving files between layers, creating ports/adapters/use-cases.

2026-02-272

docker-selfhost

pvidaal07/LifeOS

Docker Compose self-hosting conventions for LifeOS development and production. Use when editing compose files, environment variables, service networking, persistent volumes, health checks, or deployment workflows.

2026-02-272

docs

pvidaal07/LifeOS

Repository documentation conventions for LifeOS. Use when creating or updating README, docs/*, architecture notes, API behavior notes, or implementation decisions that must remain clear for future contributors and agents.

2026-02-272

name	testing-vitest
description	Vitest testing patterns for LifeOS backend and frontend. Use when adding unit/integration tests, refactoring behavior, fixing regressions, or validating business rules such as ownership and spaced review scheduling.

Testing Vitest

Objetivo

Cubrir comportamiento de negocio con tests estables, rápidos y legibles.

REQUIRED

Escribir tests AAA (Arrange, Act, Assert).
Nombrar casos en lenguaje de negocio, no de implementación.
Priorizar unit tests para lógica pura (algoritmos, validaciones, mappers).
Añadir integration tests para flujos críticos de API/repositorio.
Mockear dependencias externas (DB real, red, tiempo) cuando no sea un test de integración.
Cubrir casos borde: ownership, estados inválidos, fechas límite, respuestas vacías.

NEVER

No testear detalles internos frágiles (spies excesivos, private methods).
No depender del orden global de ejecución.
No introducir sleeps reales si se puede usar fake timers.

Estructura sugerida

Backend: backend/test/{domain,application,integration}.
Frontend: tests junto a feature o en frontend/src/test por módulo.

Flujo recomendado

Reproducir bug/regla faltante en test.
Implementar cambio mínimo.
Ejecutar suite objetivo y luego suite completa.