# 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.

## Install

```bash
npx skillstore add andrehogberg/tunit
```

## Metadata

- - Slug: andrehogberg-tunit
- - Version: 1.0.0
- - Author: AndreHogberg
- - GitHub username: AndreHogberg
- - License: MIT
- - Repository: https://github.com/AndreHogberg/summit-ui/tree/main/.claude/skills/tunit
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: external\_commands
- - Quality score: 72
- - Public page: https://skillstore.pages.dev/skills/andrehogberg-tunit
- - Manifest: https://skillstore.pages.dev/api/skills/andrehogberg-tunit/manifest

## Capabilities

- Runs the TUnit Playwright suite through dotnet run with the documented project path.
- Limits Playwright test execution to one or two parallel tests.
- Filters tests by class, exact test name, wildcard pattern, or namespace.
- Shows how to produce detailed console output and TRX reports.
- Explains project conventions for retries, server readiness, and PageTest-based tests.

## Use Cases

- 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.

## Prompt Templates

### Run every test

```
Run the full TUnit Playwright test suite and tell me whether it passes.
```

### Limit parallel execution

```
Run the TUnit Playwright tests with one parallel test so the machine stays responsive.
```

### Filter a focused group

```
Run only the SelectAccessibilityTests TUnit Playwright tests and summarize the failures.
```

### Generate triage output

```
Run the matching keyboard tests with detailed console output and a TRX report for review.
```

## Limitations

- Assumes the .NET test project exists at tests/SummitUI.Tests.Playwright.
- Does not install dotnet, TUnit, Playwright browsers, or project dependencies.
- Does not analyze failing test output without the user providing results.
- Commands may start a local server, browser processes, and repository test code.

## 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.

## Anti Patterns

- 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.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T08:51:56.592\+00:00
- - Summary: Static 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.

## Stats

- - Views: 222
- - Downloads: 4
- - Favorites: 0
- - Popularity score: 0