From photino
Run tests for a Photino.NET project with filter patterns, coverage collection, and frontend type checking
How this command is triggered — by the user, by Claude, or both
Slash command
/photino:photino-testThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run tests for a Photino.NET application. Supports filtering by class, method, category, and combined patterns, plus coverage collection and frontend type checking. ## Steps ### 1. Detect Test Project Find the test project: ### 2. Run Tests #### All Tests #### Filter Patterns #### Verbose Output ### 3. Coverage Collection Generate an HTML report: ### 4. Frontend Type Checking Run Svelte/TypeScript type checks: ### 5. Report Results Summarize: - Total tests: passed, failed, skipped - Any test failures with error messages - Coverage percentage (if collected) - Fronte...
Run tests for a Photino.NET application. Supports filtering by class, method, category, and combined patterns, plus coverage collection and frontend type checking.
Find the test project:
# Find test csproj files
find . -name "*.Tests.csproj" -o -name "*.Test.csproj" | head -5
# Or check the solution
dotnet sln list 2>/dev/null | grep -i test
dotnet test
# By class name
dotnet test --filter "FullyQualifiedName~MessageRouterTests"
# By method name
dotnet test --filter "FullyQualifiedName~ExecuteAsync_SimpleCommand"
# By trait/category
dotnet test --filter "Category=Integration"
# Exclude slow tests
dotnet test --filter "Category!=Integration"
# Combined: integration tests in a specific class
dotnet test --filter "Category=Integration&FullyQualifiedName~PowerShell"
# By namespace
dotnet test --filter "FullyQualifiedName~MyApp.Tests.PowerShell"
# Show individual test results
dotnet test -v normal
# Show detailed output including test names
dotnet test --logger "console;verbosity=detailed"
# Run with coverage collection
dotnet test --collect:"XPlat Code Coverage"
# Find the coverage report
find . -name "coverage.cobertura.xml" -path "*/TestResults/*"
Generate an HTML report:
# Install report generator (one-time)
dotnet tool install -g dotnet-reportgenerator-globaltool
# Generate HTML report
reportgenerator \
-reports:"**/TestResults/*/coverage.cobertura.xml" \
-targetdir:"coverage-report" \
-reporttypes:Html
Run Svelte/TypeScript type checks:
# Navigate to frontend project
cd <frontend-path>
# Run type checker
pnpm run check
# Typically: svelte-check --tsconfig ./tsconfig.json
Summarize:
| Filter | Command |
|---|---|
| All tests | dotnet test |
| One class | dotnet test --filter "FullyQualifiedName~ClassName" |
| One method | dotnet test --filter "FullyQualifiedName~MethodName" |
| Category | dotnet test --filter "Category=Integration" |
| Exclude category | dotnet test --filter "Category!=Integration" |
| Combined | dotnet test --filter "Category=Integration&FullyQualifiedName~PowerShell" |
| Fast only | dotnet test --filter "Category!=Integration&Category!=Live" |
[Trait("Environment", "Interactive")] and skip in CI.TaskCompletionSource with timeouts.IClassFixture<> to share sessions across tests in a class.dotnet test — they use the Node.js toolchain.npx claudepluginhub standardbeagle/standardbeagle-tools --plugin photino/testRuns project test suite by auto-detecting type (Python, Node.js, Java, .NET, Go, Rust) and executing tests (pytest, npm test, mvn test, etc.). Reports pass/fail, details failures, suggests fixes.
/sc-testExecutes unit, integration, or E2E tests with coverage analysis, quality metrics, failure diagnostics, and reports. Supports watch mode, auto-fix, and Playwright browser testing.
/testExecutes unit, integration, or e2e tests with coverage analysis, quality metrics, failure diagnostics, and optional watch mode or auto-fixes.