ACTIVAR SIEMPRE que el usuario mencione tests, PHPUnit, TestCase, archivos *Test.php, o pida revisar, crear, comprobar, completar o verificar tests en FacturaScripts. No esperes a que el usuario pida "escribir un test" explícitamente — cualquier pregunta sobre si existe un test para una funcionalidad, si falta cobertura, o si un comportamiento está probado activa esta skill. Úsalo para: revisar tests existentes y detectar casos que faltan, escribir tests PHPUnit para modelos y controladores, ejecutar tests (fsmaker test, composer test), análisis estático con PHPStan, verificación de estilo con CS-Check/CS-Fix, diagnóstico de errores en plugins, modo debug (FS_DEBUG), logging con Tools::log(), y verificación de que extensiones, migraciones y workers funcionan correctamente. También cubre tests contables: asientos (Asiento, Partida), subcuentas (Subcuenta, codejercicio), ejercicios (Ejercicio, loadFromDate, installAccountingPlan), tests multi-ejercicio (documento en un año, pago en otro), uso de DefaultSettingsTrait, RandomDataTrait, LogErrorsTrait y el patrón ensureExerciseWithAccountingPlan. Agente de control de calidad del equipo.
How to install testing-expert?
facturascripts/fs-claude-plugin/testing-expert
$npx -y skills add facturascripts/fs-claude-plugin --skill testing-expertInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/facturascripts/fs-claude-plugin" --skill "facturascripts/fs-claude-plugin/testing-expert"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/facturascripts/fs-claude-plugin" that are relevant to the current task. Run `npx skills add "https://github.com/facturascripts/fs-claude-plugin"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- tddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Jul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeJul 2026
- qaInteractive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues.Jul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…Jul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright.Jul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking…Jul 2026
