testing-basics

Essential testing patterns for any project.Use when: writing tests, setting up testing, or fixing test issues.Triggers: "test", "testing", "unit test", "write tests".

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

The Testing Basics skill provides a comprehensive framework for implementing essential software testing patterns across any programming language. It guides developers through the AAA (Arrange-Act-Assert) structure, helps distinguish between Unit, Integration, and E2E tests, and establishes best practices for test isolation and mocking. By focusing on meaningful code coverage and descriptive naming conventions, this skill ensures higher code quality and more maintainable test suites.

Use Cases

  • Structuring Unit Tests: Implementing the AAA (Arrange-Act-Assert) pattern to create readable and reliable tests for core business logic.
  • Test Strategy Optimization: Deciding when to use Unit, Integration, or E2E tests based on execution speed and system scope requirements.
  • Mocking External Dependencies: Setting up test isolation by mocking external APIs and services to prevent flaky tests and ensure independent execution.
  • Standardizing Test Suites: Applying consistent naming conventions (test_[what]_[condition]_[expected]) to improve team collaboration and debugging efficiency.
  • Pre-commit Quality Assurance: Using the built-in checklist to verify test coverage, naming, and performance before merging new code.
nametesting-basics
description|
Use whenwriting tests, setting up testing, or fixing test issues.
Triggers"test", "testing", "unit test", "write tests".

Testing Basics

Core testing patterns that apply to any language or framework.

Test Structure

AAA Pattern

Arrange → Act → Assert
# Arrange
user = User(name="Alice")

# Act
result = user.greet()

# Assert
assert result == "Hello, Alice!"

Test Types

Type Scope Speed When to use
Unit Single function/class Fast Core logic
Integration Multiple components Medium APIs, DB
E2E Full system Slow Critical paths

Naming Tests

test_[what]_[condition]_[expected]

Examples:

  • test_login_valid_credentials_returns_token
  • test_checkout_empty_cart_raises_error
  • test_search_no_results_returns_empty_list

What to Test

Do Test

  • Business logic
  • Edge cases
  • Error handling
  • Public interfaces

Don't Test

  • Framework code
  • Simple getters/setters
  • Implementation details
  • External services directly

Test Isolation

Each test should:

  • Run independently
  • Not depend on order
  • Clean up after itself
  • Not share state

Mocking

Mock external dependencies, not internal logic:

# Good: mock external service
@patch('app.services.email.send')
def test_signup_sends_welcome_email(mock_send):
    signup(user)
    mock_send.assert_called_once()

# Bad: mock internal implementation
@patch('app.models.user.User._validate')  # Don't do this

Coverage

  • Aim for meaningful coverage, not 100%
  • Cover happy paths first
  • Then error cases
  • Then edge cases

Quick Checklist

Before committing:

  • Tests pass locally
  • New code has tests
  • No flaky tests added
  • Test names are descriptive