donate-a-pytest 0.1.6

A pytest extension for sharing test cases

Donate-a-pytest

A pytest extension for sharing test cases.

Installation

pip install donate-a-pytest

Usage

Donating Tests

To donate test cases for a function, use the register_for_donation decorator:

from donate_a_pytest.decorators import register_for_donation

@register_for_donation
def my_function(param1, param2):
    # Your function implementation
    return result

This decorator does two things:

1. It returns the original function so it can be used normally
2. It creates a test function named test_my_function that will be collected by pytest

The test function will automatically run all test cases found for my_function.

Auto-discovery of Tests in Non-test Files

Normally, pytest only discovers tests in files that have a test_ prefix or _test.py suffix. However, this package extends pytest to discover tests in any Python file that contains functions decorated with @register_for_donation.

This means you can organize your code naturally without having to separate your functions into test files:

# In a regular file named my_functions.py (no test_ prefix)
from donate_a_pytest import register_for_donation

@register_for_donation
def calculate_sum(a, b):
    return a + b

# When running pytest, the test_calculate_sum function
# will be automatically discovered and run

When you run pytest, it will automatically find and run these tests, even though they're not in test files.

Using the Custom Marker

When the package is installed, it automatically registers a custom pytest marker donate. You can use it in two ways:

1. Automatically: The @register_for_donation decorator applies the marker to the generated test functions

2. Manually: Apply the marker to any test function directly

   from donate_a_pytest import donate
   
   @donate
   def test_my_custom_function():
       # Test implementation
       assert True
   

The marker is properly registered with pytest, so you won't see any warnings about unknown markers.

Interface Functions

donate-a-pytest provides a set of interface functions for programmatically registering and retrieving test cases without relying on JSON or YAML files:

1. Registering Individual Test Cases

from donate_a_pytest import register_test_case, TestCase

# Register a test case for a function
register_test_case(
    "add_numbers",  # Function name
    TestCase(input={"a": 1, "b": 2}, output=3, description="Simple addition")
)

2. Registering Test Cases with Individual Parameters

from donate_a_pytest import register

# Register a test case by specifying input, output and description
register(
    func_name="multiply_numbers",
    inp={"x": 5, "y": 4},
    outp=20,
    desc="Multiplying 5 and 4"
)

3. Registering Multiple Test Cases at Once

from donate_a_pytest import register_test_cases, TestCase

# Create multiple test cases
test_cases = [
    TestCase(input={"text": "hello"}, output="HELLO", description="Uppercase conversion"),
    TestCase(input={"text": "WORLD"}, output="WORLD", description="Already uppercase")
]

# Register all test cases for a function
register_test_cases("to_uppercase", test_cases)

4. Retrieving Test Cases for a Function

from donate_a_pytest import get_test_cases

# Get all test cases for a specific function
cases = get_test_cases("add_numbers")
print(f"Found {len(cases)} test cases for add_numbers")

5. Retrieving All Registered Test Cases

from donate_a_pytest import get_all_test_cases

# Get all registered test cases across all functions
all_cases = get_all_test_cases()
for func_name, cases in all_cases.items():
    print(f"Function {func_name} has {len(cases)} test cases")

Supported Output Types

The framework supports any output type, not just dictionaries. You can return:

• Basic types (int, float, str, bool)
• Collections (lists, tuples, dictionaries)
• None values
• Any other serializable type

Here's an example with different return types:

@register_for_donation
def process_data(a, b):
    if isinstance(a, int) and isinstance(b, int):
        return a + b  # Returns an integer
    elif isinstance(a, str) and isinstance(b, str):
        return a + " " + b  # Returns a string
    elif isinstance(a, list) and isinstance(b, list):
        return a + b  # Returns a list
    elif isinstance(a, dict) and isinstance(b, dict):
        return {**a, **b}  # Returns a dictionary
    return None  # Returns None

Running Donated Tests

You can run all tests marked with the donate marker using the provided CLI:

# Run all donated tests in the current directory
donate-pytest

# Run with verbose output
donate-pytest -v

# Specify a directory to search for tests
donate-pytest -d path/to/tests

# Stop on first failure
donate-pytest -f

You can also run them directly with pytest:

# Run all tests with the donate marker
pytest -m donate

Programmatic Usage

You can also run the tests programmatically:

from donate_a_pytest import run_donated_tests

results = run_donated_tests(
    directory="path/to/tests",
    verbose=True,
    output_format="summary",
    failfast=False
)
print(f"Tests {'passed' if results['success'] else 'failed'}")

Test Case Format

Test cases are stored in JSON or YAML files that match the function name. Each test case should include:

• input: A dictionary of input parameters for the function
• output: The expected output from the function (can be any type)
• description (optional): A description of the test case

Example JSON:

[
  {
    "input": {"param1": "value1", "param2": 42},
    "output": "expected result",
    "description": "Test with string and integer parameters"
  },
  {
    "input": {"a": 1, "b": 2},
    "output": 3,
    "description": "Returns an integer"
  },
  {
    "input": {"a": [1, 2], "b": [3, 4]},
    "output": [1, 2, 3, 4],
    "description": "Returns a list"
  }
]

Example YAML:

- input:
    param1: value1
    param2: 42
  output: expected result
  description: Test with string and integer parameters

- input:
    a: 1
    b: 2
  output: 3
  description: Returns an integer

Contributing

Running Tests

Before submitting a pull request or requesting changes, please ensure all unit tests pass. This helps maintain code quality and prevents regressions.

To run the tests:

# Run all tests
pytest

# Run only tests related to donated tests
pytest -m donate

# Run with coverage report
pytest --cov=donate_a_pytest

# Run a specific test file
pytest tests/test_decorator.py

The test suite includes:

• Unit tests for core functionality
• Integration tests for the decorators
• Tests for different output types
• Tests for CLI functionality

If you're adding new features, please include appropriate tests. The test coverage should remain above 90%.

Continuous Integration

This project uses GitHub Actions for continuous integration. Every push and pull request triggers:

1. Pre-commit checks - Ensures code quality using the pre-commit hooks
2. Tests - Runs the test suite on multiple Python versions (3.8, 3.9, 3.10, 3.11)

You can see the CI workflow configuration in .github/workflows/python-tests.yml.

To run the same checks locally before committing:

# Install pre-commit hooks
pre-commit install

# Run pre-commit checks manually
pre-commit run --all-files

Test Data

When working with test data, you can add examples to the tests/test_data directory. This helps verify that your changes work correctly with different types of inputs and outputs.

License

MIT License