tunit
Run TUnit Playwright Tests Reliably
End-to-end test runs can overload local systems or miss useful filters. This skill gives Claude, Codex, and Claude Code concise TUnit commands for controlled Playwright execution.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "tunit". Run all TUnit Playwright tests with limited parallelism.
Expected outcome:
The assistant runs the documented test project with one or two parallel tests, then reports pass status, failures, and relevant timing.
Using "tunit". Run only tests matching a keyboard pattern.
Expected outcome:
The assistant applies the TUnit tree node filter for keyboard-named tests and summarizes the selected test results.
Using "tunit". Create a report for the Playwright test run.
Expected outcome:
The assistant uses the report option, explains where the report was generated, and highlights any failed tests.
Security Audit
Medium RiskStatic analysis reported many external command hits plus weak cryptography and network reconnaissance indicators. Manual review found the weak cryptography and network reconnaissance indicators are false positives from Markdown text, while the external commands are legitimate dotnet test examples. Risk is medium because the skill directs agents to execute local test projects, which can run repository code and start Playwright resources.
Medium Risk Issues (1)
Low Risk Issues (1)
Risk Factors
⚙️ External commands (6)
Detected Patterns
Quality Score
What You Can Build
Run the full suite before a release
A QA engineer can execute all TUnit Playwright tests with reduced parallelism to avoid local resource pressure.
Debug one component test
A frontend engineer can filter by class or exact test name when working on a focused UI change.
Collect test reports for review
A CI maintainer can request console details or TRX output when comparing local and pipeline results.
Try These Prompts
Run the full TUnit Playwright test suite and tell me whether it passes.
Run the TUnit Playwright tests with one parallel test so the machine stays responsive.
Run only the SelectAccessibilityTests TUnit Playwright tests and summarize the failures.
Run the matching keyboard tests with detailed console output and a TRX report for review.
Best Practices
- Use limited parallelism first when running browser-based tests locally.
- Filter by class or exact test name before rerunning an entire suite.
- Review test project code before allowing commands from a community skill to execute.
Avoid
- Do not run the full browser suite repeatedly when a focused filter is enough.
- Do not assume dependencies or Playwright browsers are installed without checking.
- Do not ignore failed setup or server readiness errors in the test output.