tunit
Run TUnit tests with Playwright
Blazor component testing requires running TUnit with Playwright. This skill provides commands to execute tests, filter by name, run in debug mode, and generate reports.
Descargar el ZIP de la skill
Subir en Claude
Ve a Configuración → Capacidades → Skills → Subir skill
Activa y empieza a usar
Pruébalo
Usando "tunit". Run TUnit tests with Playwright
Resultado esperado:
- Running all TUnit tests with Playwright
- Starting Blazor server on test URL
- Executing tests sequentially with limited parallelism
- Test Results: All tests passed
- Duration: Complete in expected time
Usando "tunit". Run specific test by name
Resultado esperado:
- Filtering tests by name pattern
- Running single test: Trigger_ShouldHave_RoleCombobox
- Test passed successfully
Usando "tunit". Generate test report
Resultado esperado:
- Running tests with TRX report output
- Report generated at test_results.trx
- Summary: 45 passed, 0 failed
Auditoría de seguridad
SeguroDocumentation-only skill containing test execution instructions. Contains bash command examples for running TUnit tests with Playwright. No executable code, no network calls, no file system access beyond standard documentation. Pure prompt-based skill with safe behavior matching stated purpose. All 47 static findings are false positives from pattern matching on documentation text.
Factores de riesgo
🌐 Acceso a red (2)
📁 Acceso al sistema de archivos (1)
⚙️ Comandos externos (33)
Puntuación de calidad
Lo que puedes crear
Run component tests
Execute accessibility and behavior tests for Blazor UI components
Filter specific tests
Run specific test suites or individual tests by name pattern
Generate test reports
Run tests with TRX output for integration with build systems
Prueba estos prompts
Run TUnit tests with Playwright
Run the test named Trigger_ShouldHave_RoleCombobox using TUnit
Run tests in debug mode so I can step through the code
Run all accessibility tests matching Keyboard* pattern
Mejores prácticas
- Limit parallel tests to prevent browser resource exhaustion
- Use test filters to run specific suites during development
- Generate TRX reports for CI/CD integration
Evitar
- Running all tests with maximum parallelism on every change
- Skipping test reports in CI pipelines
- Running debug mode without attaching a debugger
Preguntas frecuentes
What is TUnit?
Does this work with WebAssembly tests?
How many parallel tests should I run?
Is my data safe when running tests?
Why do tests sometimes fail intermittently?
How is this different from other test runners?
Detalles del desarrollador
Estructura de archivos
📄 SKILL.md