Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
poteto avatar

Testing

  • 32 installs
  • 217 repo stars
  • Updated March 19, 2026
  • poteto/noodle

testing is a Claude Code skill for testing & qa.

About

testing is a Claude Code skill for testing & qa. It helps solo builders move faster with AI-assisted development.

  • testing
  • Testing & QA
  • AI-coding skill

Testing by the numbers

  • 32 all-time installs (skills.sh)
  • Ranked #1,340 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/poteto/noodle --skill testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs32
repo stars217
Last updatedMarch 19, 2026
Repositorypoteto/noodle

How do I helps with testing & qa tasks.?

Helps with testing & qa tasks.

Who is it for?

Best when you're working on testing & qa and need structured help with testing.

Skip if: Teams with no testing & qa needs, or anyone wanting a generic chat assistant without this specific workflow.

When should I use this skill?

When you need to helps with testing & qa tasks., or when testing is a claude code skill for testing & qa.

What you get

Structured output aligned to testing: testing, Testing & QA.

Files

SKILL.mdMarkdownGitHub ↗

Testing

Test-driven by default. Prove the problem before solving it.

Core Workflow: Bug First

1. Reproduce — Run the failing scenario and observe the actual behavior 2. Write a failing test — Minimal reproduction as a test case 3. Commit the failing test — Use Skill(commit) with message like test: reproduce #issue-description 4. Fix the code — Only now attempt the fix 5. Verify — Run pnpm test and confirm the test passes 6. Commit the fix — Separate commit from the test

This applies to all bug fixes. The failing test proves the bug exists and prevents regressions.

Fixture Tests

Noodle uses directory-based fixtures in testdata/. Read references/fixtures.md for full format, helper API, and code patterns.

Creating a New Fixture

./scripts/scaffold-fixture.sh <package-dir> <fixture-name> [state-count]

Fill in the generated input.json/input.ndjson and expected.md, then:

pnpm fixtures:hash:sync

Bug Fixtures

See references/fixtures.md for full bug fixture format (frontmatter fields, expected error sections, and the fix workflow).

Key Commands

CommandPurpose
pnpm testRun all tests
pnpm test:shortSkip integration tests
pnpm checkFull local CI (test + vet + lint + fixtures)
pnpm bugsList fixtures marked as known bugs
pnpm fixtures:loopVerify loop fixtures match expected
pnpm fixtures:loop:recordRegenerate loop fixture expected output
pnpm fixtures:hashVerify fixture input hashes
pnpm fixtures:hash:syncUpdate fixture input hashes
pnpm vetRun go vet
pnpm lint:archArchitecture lint (file sizes, legacy patterns)

Running Specific Tests

# Single package
go test ./loop

# Single test
go test ./loop -run TestLoopDirectoryFixtures

# Bypass cache
go test -count=1 ./parse

# With race detector
go test -race ./...

# Verbose
go test -v ./tui

Integration Tests

Long-running or external-dependency tests use testing.Short():

if testing.Short() {
    t.Skip("skipping integration test in short mode")
}

pnpm test:short skips these. pnpm test runs everything.

Related skills

FAQ

What does testing do?

testing is a Claude Code skill for testing & qa.

When should I use testing?

When you need to helps with testing & qa tasks., or when testing is a claude code skill for testing & qa.

What are the main capabilities?

testing; Testing & QA; AI-coding skill.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.