Test

Skill SoftwareOneHN/dev-kit/references/test

🛠️ Dev Kit — lifecycle-driven Agent Skill for structured development workflows. Brainstorm, plan, implement, debug, fix, test & adversarial code review. Java/Spring Boot + TypeScript/React/Vue rules included. Compatible with Claude Code, Cursor, Kiro, and 40+ agentic clients.

Install

npx -y skills add SoftwareOneHN/dev-kit --skill test

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.

SKILL.md

5.2 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

Testing & Quality Assurance

Comprehensive testing framework covering code-level testing (unit, integration, e2e), UI/visual testing via browser automation, coverage analysis, and structured QA reporting.

Default (No Arguments)

If invoked with context (test scope), proceed with testing. If invoked WITHOUT arguments, use AskUserQuestion to present available test operations:

Operation	Description
`(default)`	Run unit/integration/e2e tests
`ui`	Run UI tests on a website

Present as options via AskUserQuestion with header "Test Operation", question "What would you like to do?".

Core Principle

NEVER IGNORE FAILING TESTS. Fix root causes, not symptoms. No mocks/cheats/tricks to pass builds.

When to Use

After implementation: Validate new features or bug fixes
Coverage checks: Ensure coverage meets project thresholds (80%+)
UI verification: Visual regression, responsive layout, accessibility
Build validation: Verify build process, dependencies, CI/CD compatibility
Pre-commit/push: Final quality gate

Workflows

1. Code Testing (`references/test-execution-workflow.md`)

Execute test suites, analyze results, generate coverage. Supports JS/TS (Jest/Vitest/Mocha), Python (pytest), Go, Rust, Flutter. Includes working process, quality standards, and tool commands.

Load when: Running unit/integration/e2e tests, checking coverage, validating builds

2. UI Testing (`references/ui-testing-workflow.md`)

Browser-based visual testing via agent-browser, web-testing, chrome-profile, or project-native Playwright/Vitest/k6 commands. Covers screenshots, responsive checks, accessibility audits, form automation, and console error collection.

Load when: Visual regression testing, UI bugs, responsive layout checks, accessibility audits

3. Report Format (`references/report-format.md`)

Structured QA report template: test results overview, coverage metrics, failed tests, performance, build status, recommendations.

Load when: Generating test summary reports

Quick Reference

Code tests     → test-execution-workflow.md
  npm test / pytest / go test / cargo test / flutter test
  Coverage: npm run test:coverage / pytest --cov

UI tests       → ui-testing-workflow.md
  Screenshots, responsive, a11y, forms, console errors
  Auth: chrome-profile for real user login/cookies, or project-native test setup

Reports        → report-format.md
  Structured QA summary with metrics & recommendations

Working Process

Identify testing scope from recent changes or requirements
Run typecheck/analyze commands to catch syntax errors first
Execute appropriate test suites
Analyze results — focus on failures
Generate coverage reports if applicable
For frontend: run UI tests via agent-browser, web-testing, chrome-profile, or project-native browser tests
Produce structured summary report

Tools Integration

Test runners: Jest, Vitest, Mocha, pytest, go test, cargo test, flutter test
Coverage: Istanbul/c8/nyc, pytest-cov, go cover
Browser: agent-browser for live browser testing without real user cookies; chrome-profile for the user's actual Chrome login state; web-testing or project-native Playwright/Vitest/k6 for repeatable UI tests
Analysis: ai-multimodal skill for screenshot analysis
Debugging: debug skill when tests reveal bugs requiring investigation
Thinking: sequential-thinking skill for complex test failure analysis

Quality Standards

All critical paths must have test coverage
Validate happy path AND error scenarios
Ensure test isolation — no interdependencies
Tests must be deterministic and reproducible
Clean up test data after execution
Never ignore failing tests to pass the build

Report Output

IMPORTANT: Invoke "/project-organization" skill to organize the outputs.

Use naming pattern from ## Naming section injected by hooks.

Team Mode

When operating as teammate:

On start: check TaskList, claim assigned/next unblocked task via TaskUpdate
Read full task description via TaskGet before starting
Wait for blocked tasks (implementation) to complete before testing
Respect file ownership — only create/edit test files assigned
When done: TaskUpdate(status: "completed") then SendMessage results to lead

Fallback: Task tools (TaskList/TaskUpdate/TaskGet) are CLI-only — unavailable in VSCode extension. If they error, use TodoWrite for progress tracking and coordinate via SendMessage only.

Workflow Position

Typically follows: /cook (test after implementation), /fix (test after bug fix) Typically precedes: /code-review (review after tests pass) Related: /cook (implement then test), /fix (fix then test)

Gives 0 of the 12 instructions most e2e browser skills give in ~1.1k tokens

Counted across 407 of the 410 authors here whose files we hold, read 2026-08-06

use page object model patternin 35 of 407, across 25 files
Snapshot to get element refsin 24 of 407, across 14 files
keep tests independentin 23 of 407, across 18 files
Interact using refs from the latest snapshotin 23 of 407, across 11 files
clean up test data after each testin 21 of 407, across 15 files
test user behavior not implementationin 20 of 407, across 14 files
quarantine flaky tests explicitlyin 19 of 407, across 10 files
wait for specific network conditionsin 18 of 407, across 8 files
re-snapshot after navigation or dom changesin 17 of 407, across 10 files
Detect running dev servers before writing test codein 17 of 407, across 7 files
use web-first assertionsin 17 of 407, across 14 files
capture screenshots or videos on test failurein 17 of 407, across 14 files

Said here and by no other author read

ask user for test operation when no arguments provided
identify testing scope from recent changes
run typecheck or analyze commands before tests
execute appropriate test suites
analyze test results focusing on failures
run UI tests for frontend changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.