Agent skill

Test Expert

by einverne in einverne/dotfiles

Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks.

GPL-3.0Auto-check passedTesting & QA

Install Test Expert

skills CLI
$ npx skills add einverne/dotfiles --skill test-expert -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install einverne/dotfiles test-expert --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/einverne/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/test-expert .claude/skills/test-expert && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-expert
GitHub stars
121
Token cost
~2.3k tokens
SKILL.md length
357 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
GPL-3.0

At a glance

Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks.

  • Works in 3 steps: Test Pyramid → FIRST Principles → Test Coverage Goals
  • The user needs to write tests
  • SKILL.md covers Testing Principles, Test-Driven Development (TDD), Unit Testing and Testing by Language, plus 5 more sections
  • Calls pytest and jest

What it does

Test Expert is an agent skill from einverne/dotfiles. Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks. Use when the user needs to write tests, implement TDD, or improve test coverage and quality.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test-driven development, Test coverage and Test strategy. The repository describes itself as: my personal dotfiles managed by dotbot, zinit. The licence is GPL-3.0.

When your agent uses it

  • The user needs to write tests
  • Improve test coverage and quality

Example prompts

  • “/test-expert”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Test Pyramid
  2. FIRST Principles
  3. Test Coverage Goals

What it can do on your machine

Read from SKILL.md and the folder at commit c6c0686. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pytest
    • jest

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Expert loads about 2.3k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 357 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from einverne/dotfiles at commit c6c0686, republished under its GPL-3.0 licence (© einverne). 357 words, ~2,269 tokens.

Download SKILL.mdSave it as .claude/skills/test-expert/SKILL.md (or your agent's skills folder).
name
test-expert
description
Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks. Use when the user needs to write tests, implement TDD, or improve test coverage and quality.

You are a testing expert. Your role is to help users write effective tests, follow TDD practices, and ensure code quality through comprehensive test coverage.

Testing Principles

1. Test Pyramid
        /\
       /  \  E2E Tests (Few)
      /____\
     /      \  Integration Tests (Some)
    /________\
   /          \  Unit Tests (Many)
  /__________\
  • Unit Tests: Fast, isolated, test single components
  • Integration Tests: Test component interactions
  • E2E Tests: Test entire user flows
2. FIRST Principles
  • Fast: Tests should run quickly
  • Isolated: Tests shouldn't depend on each other
  • Repeatable: Same result every time
  • Self-Validating: Pass or fail, no manual checking
  • Timely: Write tests before or with code
3. Test Coverage Goals
  • Aim for 80%+ coverage
  • 100% coverage for critical paths
  • Focus on important business logic
  • Don't test framework code
  • Don't obsess over 100%

Test-Driven Development (TDD)

Red-Green-Refactor Cycle
  1. Red: Write a failing test
python
def test_add_numbers():
    assert add(2, 3) == 5  # Function doesn't exist yet
  1. Green: Write minimal code to pass
python
def add(a, b):
    return a + b
  1. Refactor: Improve code quality
python
def add(a: int, b: int) -> int:
    """Add two numbers and return the result."""
    return a + b
TDD Benefits
  • Forces you to think about API design
  • Ensures testable code
  • Provides immediate feedback
  • Creates living documentation
  • Prevents over-engineering

Unit Testing

Good Unit Test Characteristics
python
# Good: Clear, focused, independent
def test_user_can_be_created_with_email():
    # Arrange
    email = "user@example.com"

    # Act
    user = User(email=email)

    # Assert
    assert user.email == email
    assert user.is_active == True
AAA Pattern
  • Arrange: Set up test data
  • Act: Execute the code under test
  • Assert: Verify the result
Test Naming
python
# Good names describe what's being tested
def test_user_creation_with_valid_email_succeeds():
    pass

def test_user_creation_with_invalid_email_raises_error():
    pass

def test_empty_cart_has_zero_total():
    pass

Testing by Language

Python (pytest)
python
import pytest
from myapp import Calculator

class TestCalculator:
    @pytest.fixture
    def calc(self):
        return Calculator()

    def test_add(self, calc):
        assert calc.add(2, 3) == 5

    def test_divide_by_zero_raises_error(self, calc):
        with pytest.raises(ZeroDivisionError):
            calc.divide(10, 0)

    @pytest.mark.parametrize("a,b,expected", [
        (2, 3, 5),
        (0, 0, 0),
        (-1, 1, 0),
    ])
    def test_add_multiple_cases(self, calc, a, b, expected):
        assert calc.add(a, b) == expected
JavaScript (Jest)
javascript
describe('Calculator', () => {
  let calc;

  beforeEach(() => {
    calc = new Calculator();
  });

  test('adds two numbers', () => {
    expect(calc.add(2, 3)).toBe(5);
  });

  test('throws error on division by zero', () => {
    expect(() => calc.divide(10, 0)).toThrow();
  });

  test.each([
    [2, 3, 5],
    [0, 0, 0],
    [-1, 1, 0],
  ])('add(%i, %i) returns %i', (a, b, expected) => {
    expect(calc.add(a, b)).toBe(expected);
  });
});
Shell Scripts (bats)
bash
#!/usr/bin/env bats

@test "script exits with status 0 on success" {
  run ./myscript.sh input.txt
  [ "$status" -eq 0 ]
}

@test "script produces expected output" {
  run ./myscript.sh input.txt
  [ "${lines[0]}" = "Expected output" ]
}

@test "script fails with invalid input" {
  run ./myscript.sh nonexistent.txt
  [ "$status" -ne 0 ]
  [[ "$output" =~ "Error" ]]
}

Mocking and Stubbing

When to Mock
  • External services (APIs, databases)
  • Slow operations
  • Non-deterministic behavior (random, time)
  • Hard-to-trigger scenarios (errors)
Python Mocking
python
from unittest.mock import Mock, patch, MagicMock

# Mock an object
mock_db = Mock()
mock_db.get_user.return_value = {"id": 1, "name": "Test"}

# Patch a function
@patch('myapp.external_api_call')
def test_function(mock_api):
    mock_api.return_value = {"status": "success"}
    result = my_function()
    assert result == expected
    mock_api.assert_called_once_with(expected_arg)
JavaScript Mocking
javascript
// Jest mocking
jest.mock('./api');
import { fetchUser } from './api';

test('loads user data', async () => {
  fetchUser.mockResolvedValue({ id: 1, name: 'Test' });

  const user = await loadUser(1);

  expect(user.name).toBe('Test');
  expect(fetchUser).toHaveBeenCalledWith(1);
});

Integration Testing

Database Testing
python
import pytest
from myapp import create_app, db

@pytest.fixture
def app():
    app = create_app('testing')
    with app.app_context():
        db.create_all()
        yield app
        db.session.remove()
        db.drop_all()

def test_user_can_be_saved_to_database(app):
    user = User(email='test@example.com')
    db.session.add(user)
    db.session.commit()

    retrieved = User.query.filter_by(email='test@example.com').first()
    assert retrieved is not None
    assert retrieved.email == 'test@example.com'
API Testing
python
def test_api_returns_user_list(client):
    response = client.get('/api/users')

    assert response.status_code == 200
    assert len(response.json) > 0
    assert 'email' in response.json[0]
Show full SKILL.md (142 more words)Show less

End-to-End Testing

Web Testing (Playwright/Selenium)
javascript
// Playwright example
test('user can login', async ({ page }) => {
  await page.goto('https://example.com');

  await page.fill('[name="email"]', 'user@example.com');
  await page.fill('[name="password"]', 'password123');
  await page.click('button[type="submit"]');

  await expect(page.locator('.welcome')).toContainText('Welcome back');
});

Test Fixtures and Factories

Fixtures
python
@pytest.fixture
def sample_user():
    return User(
        email='test@example.com',
        name='Test User'
    )

@pytest.fixture
def authenticated_client(client, sample_user):
    client.login(sample_user)
    return client
Factories
python
import factory

class UserFactory(factory.Factory):
    class Meta:
        model = User

    email = factory.Sequence(lambda n: f'user{n}@example.com')
    name = factory.Faker('name')
    is_active = True

# Usage
user = UserFactory()
admin = UserFactory(is_admin=True)
users = UserFactory.create_batch(10)

Testing Best Practices

Do's
  • ✅ Write tests first (TDD)
  • ✅ Test behavior, not implementation
  • ✅ Keep tests simple and readable
  • ✅ Use descriptive test names
  • ✅ Test edge cases and errors
  • ✅ Keep tests fast
  • ✅ Make tests independent
  • ✅ Use fixtures for common setup
Don'ts
  • ❌ Test framework/library code
  • ❌ Test multiple things in one test
  • ❌ Use random data without seeding
  • ❌ Depend on test execution order
  • ❌ Leave commented-out tests
  • ❌ Skip tests without good reason
  • ❌ Have flaky tests

Test Organization

project/
├── src/
│   └── myapp/
│       ├── __init__.py
│       └── calculator.py
└── tests/
    ├── __init__.py
    ├── conftest.py          # Shared fixtures
    ├── unit/
    │   └── test_calculator.py
    ├── integration/
    │   └── test_database.py
    └── e2e/
        └── test_user_flow.py

Code Coverage

Generate Coverage Report
bash
# Python
pytest --cov=myapp --cov-report=html

# JavaScript
jest --coverage

# View coverage
open htmlcov/index.html
Coverage Goals
  • Critical business logic: 100%
  • Most code: 80%+
  • E2E scripts: Lower coverage OK
  • Don't sacrifice test quality for coverage numbers

Common Testing Patterns

Testing Exceptions
python
def test_raises_error():
    with pytest.raises(ValueError, match="Invalid input"):
        function_that_raises("bad")
Testing Async Code
python
@pytest.mark.asyncio
async def test_async_function():
    result = await async_function()
    assert result == expected
Testing Time-Dependent Code
python
@patch('myapp.datetime')
def test_time_dependent(mock_datetime):
    mock_datetime.now.return_value = datetime(2024, 1, 1)
    result = function_using_time()
    assert result == expected

Continuous Integration

yaml
# .github/workflows/test.yml
name: Tests
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Run tests
        run: |
          pip install -r requirements-dev.txt
          pytest --cov --cov-report=xml
      - name: Upload coverage
        uses: codecov/codecov-action@v2

Remember: Good tests are your safety net. They give you confidence to refactor and add features. Invest time in writing quality tests!

© einverne, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in claude/skills/test-expert of einverne/dotfiles.

Open the folder on GitHubat commit c6c0686

Compare with similar skills

Test Expert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Expert compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Expert this skilleinverne/dotfiles121—~2.3kAutomated safety check: PassGPL-3.0
Recommending Test Layersbitwarden/ai-plugins154—~2.4kAutomated safety check: PassCustom licence
Test Automationrevfactory/harness-1001.3k—~1.7kAutomated safety check: PassApache-2.0
Python Testingathola/claude-night-market341—~800Automated safety check: PassMIT
Designing TestsCloudAI-X/opencode-workflow275—~2.9kAutomated safety check: PassMIT
Automated Test Planningtestdouble/han279—~6.7kAutomated safety check: PassMIT

Similar skills

  • Recommending Test Layers

    bitwarden/ai-plugins

    Official

    A skill your agent uses when deciding WHICH new tests a change needs and at WHICH layer each belongs, working from a Jira key, a Testmo CSV, an assessing-test-coverage report, a PR, or a feature…

    154 GitHub stars~2.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Test Automation

    revfactory/harness-100

    A full test automation pipeline. An agent skill from revfactory/harness-100.

    1.3k GitHub stars~1.7k tokensUpdated 6 mo ago
    Testing & QAAuto-check passed
  • Python Testing

    athola/claude-night-market

    Python testing patterns with pytest, fixtures, TDD, mocking, async and integration tests.

    341 GitHub stars~800 tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • Designing Tests

    CloudAI-X/opencode-workflow

    Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.

    275 GitHub stars~2.9k tokensUpdated 9 mo ago
    Testing & QAAuto-check passed
  • Produce a standalone test plan by analyzing code for test coverage gaps and edge cases.

    279 GitHub stars~6.7k tokensUpdated 8 days ago
    Testing & QAAuto-check passed
  • Memstack Development Test Writer

    cwinvestments/memstack

    A skill your agent uses when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with…

    423 GitHub stars~3.7k tokensUpdated 13 days ago
    Testing & QAAuto-check passed

More from einverne/dotfiles

All 39 skills in this repo
  • DOCX

    einverne/dotfiles

    Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction.

    121 GitHub starsUsed in 35 repos~2.5k tokens
    Auto-check: notes
  • Chrome Devtools

    einverne/dotfiles

    Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.

    121 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check: notes
  • PDF

    einverne/dotfiles

    Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms.

    121 GitHub starsUsed in 47 repos~1.8k tokens
    Auto-check passed
  • Gemini Audio

    einverne/dotfiles

    Guide for implementing Google Gemini API audio capabilities - analyze audio with transcription, summarization, and understanding (up to 9.5 hours), plus generate speech with controllable TTS.

    121 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Guide for implementing Google Gemini API document processing - analyze PDFs with native vision to extract text, images, diagrams, charts, and tables.

    121 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check: notes
  • PPTX

    einverne/dotfiles

    Presentation creation, editing, and analysis. An agent skill from einverne/dotfiles.

    121 GitHub starsUsed in 38 repos~6.4k tokens
    Auto-check: notes

Categories

Questions about Test Expert

What does Test Expert do?

Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks. Test Expert is an agent skill from einverne/dotfiles. Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks.

When should I use Test Expert?

Test Expert fits situations like: the user needs to write tests; improve test coverage and quality.

How do I install Test Expert in Claude Code?

Run `npx skills add einverne/dotfiles --skill test-expert -a claude-code`. Or copy the skill folder (claude/skills/test-expert in einverne/dotfiles) into .claude/skills/test-expert in your project. Claude Code loads it when a task matches its description.

How do I install Test Expert in Codex?

Run `npx skills add einverne/dotfiles --skill test-expert -a codex`. Or copy the skill folder (claude/skills/test-expert in einverne/dotfiles) into .agents/skills/test-expert in your project. Codex loads it when a task matches its description.

Can I use Test Expert in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add einverne/dotfiles --skill test-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-expert, .gemini/skills/test-expert, .github/skills/test-expert and .opencode/skills/test-expert in your project.

What does Test Expert need to run?

Going by SKILL.md and its folder, Test Expert needs the command-line tools its instructions call (pytest and jest). Our summary lists: Python 3.

Does Test Expert access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Expert safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Expert use?

Test Expert is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Expert use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Test Expert?

Skills that share tags, products or a category with Test Expert: Recommending Test Layers (bitwarden/ai-plugins, 154 stars), Test Automation (revfactory/harness-100, 1.3k stars), Python Testing (athola/claude-night-market, 341 stars) and Designing Tests (CloudAI-X/opencode-workflow, 275 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Expert?

einverne (a GitHub user) maintains it in einverne/dotfiles, which has 121 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 9, 2026.

Source: einverne/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.