AP

api-test-generator

Automates the creation of robust pytest tests for REST APIs by analyzing DataStructure.php definitions.

Install

mkdir -p .claude/skills/api-test-generator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4940" && unzip -o skill.zip -d .claude/skills/api-test-generator && rm skill.zip

Installs to .claude/skills/api-test-generator

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Генерация полных Python pytest тестов для REST API эндпоинтов с валидацией схемы. Использовать при создании тестов для новых эндпоинтов, добавлении покрытия для CRUD операций или валидации соответствия API с OpenAPI схемами.
224 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Locates DataStructure.php files via grep
  • Extracts parameter types, constraints, and enums
  • Generates pytest suites from templates
  • Produces CRUD-specific test logic
  • Validates OpenAPI schema structures

How it works

It parses DataStructure.php files to extract API definitions and injects them into a pre-defined test-template.py file to ensure coverage.

Inputs & outputs

You give it
API endpoint path and resource name
You get back
Complete Python pytest file with CRUD and schema validations

When to use api-test-generator

  • Testing new REST API endpoints
  • Adding test coverage for CRUD operations
  • Validating API against OpenAPI specs
  • Generating negative test cases

About this skill

MikoPBX API Test Generating

Generate comprehensive Python pytest tests for MikoPBX REST API endpoints with full parameter coverage, schema validation, and edge case testing.

What This Skill Does

Analyzes DataStructure.php files and generates complete pytest test suites including:

  • ✅ CRUD operation tests (Create, Read, Update, Delete)
  • ✅ Positive and negative test cases
  • ✅ Parameter validation tests
  • ✅ Edge cases and boundary conditions
  • ✅ Schema validation tests
  • ✅ Proper fixtures and authentication
  • ✅ Detailed assertions with error messages

When to Use This Skill

Use this skill when you need to:

  • Create pytest tests for new REST API endpoints
  • Add comprehensive test coverage for existing endpoints
  • Generate tests covering all parameter combinations
  • Add schema validation tests for API responses
  • Create edge case and negative tests
  • Ensure API compliance with OpenAPI specification

Quick Start

Basic Usage

When the user requests test generation:

  1. Identify the endpoint

    • API path (e.g., /pbxcore/api/v3/extensions)
    • HTTP methods (GET, POST, PUT, DELETE, PATCH)
    • Resource name (e.g., Extensions)
  2. Locate DataStructure.php

    find /Users/nb/PhpstormProjects/mikopbx/Core/src/PBXCoreREST/Lib -name "DataStructure.php" | grep -i "{resource}"
    
  3. Analyze parameter definitions Extract from DataStructure.php:

    • Required vs optional parameters
    • Data types and validation rules
    • Default values
    • Enum values
    • Pattern constraints (regex)
    • Min/max values
  4. Generate test file Use the complete template from test-template.py

  5. Customize for endpoint

    • Replace {ResourceName} placeholders
    • Fill in actual payload structures
    • Add specific field validations
    • Include enum and pattern validations

Test Structure

File Organization

tests/api/
├── test_{resource}_api.py        # Main test file
└── conftest.py                   # Shared fixtures

Test Class Structure

Each test file should have these test classes:

class TestCreate{ResourceName}:
    """Test POST endpoint for creating resources"""
    - test_create_with_valid_data()
    - test_create_missing_required_field()
    - test_create_with_invalid_type()

class TestGet{ResourceName}:
    """Test GET endpoint for retrieving resources"""
    - test_get_all()
    - test_get_by_id()
    - test_get_nonexistent()

class TestUpdate{ResourceName}:
    """Test PUT/PATCH endpoints for updating resources"""
    - test_update_with_valid_data()
    - test_patch_partial_update()

class TestDelete{ResourceName}:
    """Test DELETE endpoint for removing resources"""
    - test_delete_existing()
    - test_delete_nonexistent()

class TestSchemaValidation{ResourceName}:
    """Test response schema validation"""
    - test_response_matches_openapi_schema()

class TestEdgeCases{ResourceName}:
    """Test edge cases and boundary conditions"""
    - test_special_characters_in_fields()
    - test_empty_string_values()
    - test_boundary_values()

Standard Fixtures

@pytest.fixture
def auth_token():
    """Get authentication token"""
    response = requests.post(
        f"{BASE_URL}/pbxcore/api/v3/auth/login",
        json={"login": "admin", "password": "123456789MikoPBX#1"},
        verify=False
    )
    return response.json()["data"]["access_token"]

@pytest.fixture
def headers(auth_token):
    """Standard headers with authentication"""
    return {
        "Authorization": f"Bearer {auth_token}",
        "Content-Type": "application/json"
    }

Common Test Patterns

1. Create with Valid Data

def test_create_with_valid_data(self, headers):
    """Test creating a resource with all valid required parameters"""
    payload = {
        # Based on DataStructure.php
    }

    response = requests.post(
        f"{BASE_URL}{API_PATH}",
        json=payload,
        headers=headers,
        verify=False
    )

    assert response.status_code == 200, f"Expected 200, got {response.status_code}: {response.text}"
    data = response.json()
    assert "data" in data
    assert "id" in data["data"]

    # Validate returned values match input
    for key, value in payload.items():
        assert data["data"][key] == value

2. Validation Tests

def test_create_missing_required_field(self, headers):
    """Test validation when required field is missing"""
    payload = {
        # Missing required field
    }

    response = requests.post(
        f"{BASE_URL}{API_PATH}",
        json=payload,
        headers=headers,
        verify=False
    )

    assert response.status_code == 400
    assert "messages" in response.json()

3. Edge Cases

def test_special_characters_in_fields(self, headers):
    """Test handling of special characters"""
    special_chars = "Test <script>alert('xss')</script> & \"quotes\""
    payload = {
        "string_field": special_chars,
    }

    response = requests.post(...)
    assert response.status_code == 200
    assert response.json()["data"]["string_field"] == special_chars

DataStructure Analysis

When analyzing DataStructure.php, extract these key elements:

Parameter Structure

public static function getParameterDefinitions(): array
{
    return [
        'request' => [
            'POST' => [
                'parameter_name' => [
                    'type' => 'string',              // Extract type
                    'description' => 'Description',  // Extract description
                    'example' => 'value',            // Use for test data
                    'required' => true,              // Required vs optional
                    'default' => 'default_value',    // Default value
                    'enum' => ['val1', 'val2'],      // Valid enum values
                    'pattern' => '^[a-z]+$',         // Regex pattern
                    'minLength' => 1,                // Min length
                    'maxLength' => 100,              // Max length
                ],
            ],
        ],
    ];
}

Use This Data To

  1. Generate valid payloads - Use example and default values
  2. Test required fields - Create tests omitting each required field
  3. Test data types - Create tests with wrong types
  4. Test enums - Create tests for each enum value and invalid values
  5. Test patterns - Create tests for valid/invalid patterns
  6. Test boundaries - Create tests for min/max values

Test Documentation Template

Add to the top of each test file:

"""
Tests for {ResourceName} API endpoint

API Endpoint: /pbxcore/api/v3/{resource-path}
DataStructure: src/PBXCoreREST/Lib/{ResourceName}/DataStructure.php

Test Coverage:
- CRUD operations (Create, Read, Update, Delete)
- Required vs optional parameters
- Data type validations
- Enum value validations
- Pattern validations (regex)
- Boundary conditions (min/max values)
- Special characters and edge cases
- Schema validation (when SCHEMA_VALIDATION_STRICT=1)

Requirements:
- pytest
- requests
- Docker container running with MikoPBX

Run tests:
    pytest tests/api/test_{resource_name}.py -v

Run with schema validation:
    # Ensure SCHEMA_VALIDATION_STRICT=1 is set in container
    pytest tests/api/test_{resource_name}.py -v
"""

Output Format

Always generate:

  1. Complete pytest file - Runnable without modifications
  2. Documentation block - Clear description at the top
  3. All test classes - CRUD, schema validation, edge cases
  4. Proper fixtures - Authentication and headers
  5. Clear assertions - With descriptive error messages
  6. Comments - Explaining complex validations

Running Tests

Basic Execution

# Run all API tests
pytest tests/api/ -v

# Run specific endpoint tests
pytest tests/api/test_extensions_api.py -v

# Run specific test class
pytest tests/api/test_extensions_api.py::TestCreateExtensions -v

# Run specific test
pytest tests/api/test_extensions_api.py::TestCreateExtensions::test_create_with_valid_data -v

With Schema Validation

# Enable schema validation in container
docker exec mikopbx_container sh -c 'export SCHEMA_VALIDATION_STRICT=1'

# Run tests
pytest tests/api/test_extensions_api.py -v

Test Markers

# Run only CRUD tests
pytest tests/api/ -m crud -v

# Skip slow tests
pytest tests/api/ -m "not slow" -v

# Run smoke tests
pytest tests/api/ -m smoke -v

Important Notes

MikoPBX-Specific Considerations

  • Authentication: All tests need Bearer token from /auth/login
  • HTTPS: Use verify=False for self-signed certificates
  • Base URL: Default is https://mikopbx-php83.localhost:8445
  • Schema validation: Only active when SCHEMA_VALIDATION_STRICT=1 in container
  • Container restart: Changes to PHP code require container restart
  • Test isolation: Each test should be independent and idempotent

Best Practices

  1. Analyze DataStructure first - Don't guess parameter structures
  2. Include schema validation tests - Only work with SCHEMA_VALIDATION_STRICT=1
  3. Test success and failure cases - Negative tests are critical
  4. Use fixtures for auth - Avoid code duplication
  5. Clean up after tests - Delete created resources in teardown
  6. Document expected behavior - Each test should state what it validates
  7. Use descriptive test names - Clear indication of what's being tested
  8. One assertion per test - Or group related assertions

Additional Resources

Templates

Complete test templates for copy-paste usage:

Reference Documentat


Content truncated.

When not to use it

  • Non-REST API codebases
  • Projects without OpenAPI/DataStructure specifications
  • Manual test suites requiring highly custom logic

Prerequisites

bashRead access to source treegrepglob

Limitations

  • Requires predictable DataStructure.php format
  • Limited by the completeness of the source schema definitions

How it compares

Unlike a generic code-generating prompt, this tool follows a project-specific architectural pattern for MikoPBX to ensure tests are runnable and standard-compliant.

Compared to similar skills

api-test-generator side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
api-test-generator (this skill)19moReviewIntermediate
test-api-serializer04moNo flagsIntermediate
fastapi-templates5202moNo flagsIntermediate
fastapi-pro794moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

sqlite-inspector

mikopbx

Проверка консистентности данных в SQLite баз данных MikoPBX после операций REST API. Использовать при валидации результатов API, отладке проблем с данными, проверке связей внешних ключей или инспектировании CDR записей для тестирования.

568

log-analyzer

mikopbx

Анализ логов Docker контейнера для диагностики проблем и мониторинга здоровья системы. Использовать при отладке ошибок, отслеживании процессов воркеров, исследовании проблем API или мониторинге поведения системы после тестов.

213

openapi-analyzer

mikopbx

Извлечение и анализ OpenAPI 3.1.0 спецификации из MikoPBX для валидации эндпоинтов. Использовать при проверке соответствия API, генерации тестов, проверке схем эндпоинтов или интеграции с навыками endpoint-validator и api-test-generator.

25

asterisk-tester

mikopbx

Тестирование сценариев Asterisk dialplan и потоков звонков используя безопасные Local каналы. Использовать при тестировании логики маршрутизации звонков, отладке проблем dialplan или проверке потоков IVR меню.

11

asterisk-validator

mikopbx

Валидация конфигурационных файлов Asterisk и анализ логов на корректность и best practices. Использовать при отладке проблем запуска Asterisk, проверке изменений конфигурации или проверке ошибок после регенерации воркерами.

13

auth-token-manager

mikopbx

Получение валидных JWT Bearer токенов для аутентификации MikoPBX REST API v3. Использовать когда нужно тестировать API эндпоинты, отлаживать проблемы аутентификации или при возникновении ошибок 401 Unauthorized. Автоматически обрабатывает вход с username/password и возвращает готовый к использованию access token.

15

Search skills

Search the agent skills registry