SkillAgentSearch skills...

testing-patterns

Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.

Install / Use

npx skills add aiskillstore/marketplace --skill testing-patterns

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of testing-patterns

testing-patterns scores 87/100 on our quality scale, 2240th of 4,717 Development & Engineering skills we index (top 48%).

Its SKILL.md is 4.1 KB long, well organised into 19 sections with 8 code examples: a solid amount of guidance for an agent.

It has 428 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so testing-patterns is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

testing-patterns compared with similar skills

All 4 of these similar skills score higher than testing-patterns; compare them before choosing.

SkillScoreStarsUpdatedFormat
testing-patterns (this skill)by aiskillstore8742855d agoSKILL.md
taste-skillby Leonxlnx100118.3k10d agoCLAUDE.md
hyperframesby heygen-com10086.4ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10072.4ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k4d agoCLAUDE.md

Frequently asked questions

How do I install testing-patterns?
Run npx skills add aiskillstore/marketplace --skill testing-patterns. The install tabs above show the steps for each supported agent.
Which AI agents does testing-patterns work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is testing-patterns safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is testing-patterns still maintained?
The repository was last updated about 2 months ago, so testing-patterns is actively maintained.

name: testing-patterns description: "Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation." compatibility: "Language-agnostic patterns. Framework-specific details in references." allowed-tools: "Read Write Bash"

Testing Patterns

Universal testing strategies and patterns applicable across languages.

The Test Pyramid

        /\
       /  \     E2E Tests (few, slow, expensive)
      /    \    - Full system tests
     /------\   - Real browser/API calls
    /        \
   /  Integ   \ Integration Tests (some)
  /   Tests    \ - Service boundaries
 /--------------\ - Database, APIs
/                \
/   Unit Tests    \ Unit Tests (many, fast, cheap)
------------------  - Single function/class
                    - Mocked dependencies

Test Types

Unit Tests

Scope:      Single function/method/class
Speed:      Milliseconds
Dependencies: All mocked
When:       Every code change
Coverage:   80%+ of codebase

Integration Tests

Scope:      Multiple components together
Speed:      Seconds
Dependencies: Real databases, mocked external APIs
When:       PR/merge, critical paths
Coverage:   Key integration points

End-to-End Tests

Scope:      Full user journey
Speed:      Minutes
Dependencies: Real system (or staging)
When:       Pre-deploy, nightly
Coverage:   Critical user flows only

Test Naming Convention

test_<unit>_<scenario>_<expected>

Examples:
- test_calculate_total_with_discount_returns_reduced_price
- test_user_login_with_invalid_password_returns_401
- test_order_submit_when_out_of_stock_raises_error

Arrange-Act-Assert (AAA)

def test_calculate_discount():
    # Arrange - Set up test data and dependencies
    cart = Cart()
    cart.add_item(Item(price=100))
    discount = Discount(percent=10)

    # Act - Execute the code under test
    total = cart.calculate_total(discount)

    # Assert - Verify the results
    assert total == 90

Test Doubles

| Type | Purpose | Example | |------|---------|---------| | Stub | Returns canned data | stub.get_user.returns(fake_user) | | Mock | Verifies interactions | mock.send_email.assert_called_once() | | Spy | Records calls, uses real impl | spy.on(service, 'save') | | Fake | Working simplified impl | FakeDatabase() instead of real DB | | Dummy | Placeholder, never used | null object for required param |

Test Isolation Strategies

Database Isolation

Option 1: Transaction rollback (fast)
- Start transaction before test
- Rollback after test

Option 2: Truncate tables (medium)
- Clear all data between tests

Option 3: Separate database (slow)
- Each test gets fresh database

External Service Isolation

Option 1: Mock at boundary
- Replace HTTP client with mock

Option 2: Fake server
- WireMock, MSW, VCR cassettes

Option 3: Contract testing
- Pact, consumer-driven contracts

What to Test

MUST Test

  • Business logic and calculations
  • Input validation and error handling
  • Security-sensitive code (auth, permissions)
  • Edge cases and boundary conditions

SHOULD Test

  • Integration points (DB, APIs)
  • State transitions
  • Configuration handling

AVOID Testing

  • Framework internals
  • Third-party library behavior
  • Simple getters/setters
  • Private implementation details

Test Quality Checklist

  • [ ] Tests are independent (no order dependency)
  • [ ] Tests are deterministic (no flaky tests)
  • [ ] Tests are fast (unit < 100ms, integration < 5s)
  • [ ] Tests have clear names describing behavior
  • [ ] Tests cover happy path AND error cases
  • [ ] Tests don't repeat production logic
  • [ ] Mocks are minimal (only external boundaries)

Additional Resources

  • ./references/tdd-workflow.md - Test-Driven Development cycle
  • ./references/mocking-strategies.md - When and how to mock
  • ./references/test-data-patterns.md - Fixtures, factories, builders
  • ./references/ci-testing.md - Testing in CI/CD pipelines

Scripts

  • ./scripts/coverage-check.sh - Run coverage and fail if below threshold

Related Skills

View on GitHub
GitHub Stars428
CategoryDevelopment
Updated1mo ago
Forks45

Languages

Python

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium