testrail-api-module 0.8.1

A comprehensive Python wrapper for the TestRail API with enhanced error handling and performance improvements

TRAM — TestRail API Module

TRAM is a comprehensive Python wrapper for the TestRail API that provides easy access to all TestRail functionalities.

Usage

For a full consumer usage guide covering authentication, client initialization, common workflows, response shapes, exception handling, and gotchas, see USAGE.md.

Features

• NEW: Comprehensive exception handling with specific error types
• NEW: Connection pooling and automatic retry logic
• NEW: Rate limiting awareness and handling
• NEW: Configurable request timeouts
• Full coverage of TestRail API endpoints
• Type hints for better IDE support
• Easy-to-use interface
• Support for both API key and password authentication

🚨 Breaking Changes in v0.6.3

API parity audit. All endpoints were audited against the official TestRail API reference. Several methods were renamed, restructured, or removed to match the real API. See details below.

Configurations API (rewritten)

The old single-level API has been replaced with the correct two-level group/config structure:

Removed	Replacement
get_configuration(config_id)	get_configs(project_id)
get_configurations(project_id)	get_configs(project_id)
add_configuration(project_id, ...)	add_config_group(project_id, name) / add_config(config_group_id, name)
update_configuration(config_id, ...)	update_config_group(config_group_id, name) / update_config(config_id, name)
delete_configuration(config_id)	delete_config_group(config_group_id) / delete_config(config_id)

Results API (restructured)

Change	Old	New
Renamed	add_result(run_id, case_id, ...)	add_result_for_case(run_id, case_id, ...)
New	—	add_result(test_id, ...) (adds result by test ID)
New	—	get_results(test_id, ...) (gets results by test ID)
Fixed	add_results(...) called add_results_for_cases endpoint	add_results(...) now correctly calls add_results/{run_id}
Removed	add_result_for_run(...)	(not a real TestRail endpoint)

Cases API

Change	Old	New
Renamed	get_case_history(case_id)	get_history_for_case(case_id)
New	—	add_case_field(...), update_cases(...), delete_cases(...)

Plans API

Change	Old	New
Removed	get_plan_stats(plan_id)	(not a real TestRail endpoint)
New	—	add_plan_entry(...), update_plan_entry(...), delete_plan_entry(...)

New modules and methods

• Labels API (new module): get_label, get_labels, add_label, update_label, delete_label
• Sections: move_section(section_id, ...)
• Users: get_current_user()
• Statuses: get_case_statuses()
• Datasets: add_dataset(...), update_dataset(...), delete_dataset(...)

Installation

For Consumers

# Install the package with runtime dependencies only
pip install testrail-api-module

For Developers

# Clone the repository
git clone https://github.com/trtmn/testrail_api_module.git
cd testrail_api_module

# Create virtual environment and install dependencies using uv
uv venv .venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

# Install development dependencies (includes all dev tools like pytest, mypy, etc.)
uv sync --extra dev

# Or install all optional dependencies
uv sync --all-extras

Testing

# Run tests with the current Python version
uv run pytest

# Run tests across all supported Python versions (3.11, 3.12, 3.13, 3.14)
tox

Quick Start

from testrail_api_module import TestRailAPI, TestRailAPIError, TestRailAuthenticationError, TestRailRateLimitError

# Initialize the API client
api = TestRailAPI(
    base_url='https://your-instance.testrail.io',
    username='your-username',
    api_key='your-api-key',  # or use password='your-password'
    timeout=30  # Optional: request timeout in seconds
)

try:
    # Get a list of projects
    # Note: recent TestRail versions return a pagination envelope
    # ({offset, limit, size, _links, projects}) instead of a plain list.
    response = api.projects.get_projects()
    projects = response.get("projects", response)
    print(f"Found {len(projects)} projects")

    # Create a new test case
    new_case = api.cases.add_case(
        section_id=123,
        title='Test Login Functionality',
        type_id=2,  # Functional test (1 = Other)
        priority_id=3,  # Medium priority
        estimate='30m',  # 30 minutes
        refs='JIRA-123'
    )
    print(f"Created case: {new_case['title']}")

    # Add a test result for a case in a run
    result = api.results.add_result_for_case(
        run_id=456,
        case_id=789,
        status_id=1,  # Passed
        comment='Test executed successfully',
        elapsed='15m',  # Actual time taken
        version='1.0.0'
    )
    print(f"Added result: {result['id']}")

except TestRailAuthenticationError as e:
    print(f"Authentication failed: {e}")
except TestRailRateLimitError as e:
    print(f"Rate limit exceeded: {e}")
except TestRailAPIError as e:
    print(f"API error: {e}")
except Exception as e:
    print(f"Unexpected error: {e}")

Common Use Cases

Managing Test Cases

try:
    # Get all test cases in a project
    cases = api.cases.get_cases(project_id=1)
    print(f"Found {len(cases)} cases")

    # Update a test case
    updated_case = api.cases.update_case(
        case_id=123,
        title='Updated Test Case Title',
        type_id=3,  # Performance test
        priority_id=1  # Critical priority
    )
    print(f"Updated case: {updated_case['title']}")

    # Delete a test case
    result = api.cases.delete_case(case_id=123)
    print("Case deleted successfully")

except TestRailAPIError as e:
    print(f"Error managing test cases: {e}")

Working with Test Runs

# Create a new test run
new_run = api.runs.add_run(
    project_id=1,
    name='Sprint 1 Regression',
    description='Full regression test suite',
    suite_id=2,
    milestone_id=3,
    include_all=True
)

# Get the run's result counts (returned on the run itself)
run = api.runs.get_run(run_id=new_run['id'])
print(f"Passed: {run['passed_count']}, Failed: {run['failed_count']}, "
      f"Untested: {run['untested_count']}")

# Close a test run
api.runs.close_run(run_id=new_run['id'])

Managing Attachments

The attachments API uses per-entity methods that mirror the TestRail API endpoints directly. Files are uploaded as multipart form data.

# Add an attachment to a test case
result = api.attachments.add_attachment_to_case(
    case_id=123,
    file_path="path/to/screenshot.png"
)
print(f"Created attachment ID: {result['attachment_id']}")

# Add an attachment to a test run
api.attachments.add_attachment_to_run(run_id=456, file_path="report.html")

# Add an attachment to a test plan or a specific plan entry
api.attachments.add_attachment_to_plan(plan_id=10, file_path="spec.pdf")
api.attachments.add_attachment_to_plan_entry(
    plan_id=10, entry_id=5, file_path="entry_log.txt"
)

# Add an attachment to a test result
api.attachments.add_attachment_to_result(
    result_id=789, file_path="screenshot.png"
)

# Get all attachments for various entity types (supports limit/offset pagination)
attachments = api.attachments.get_attachments_for_case(case_id=123)
attachments = api.attachments.get_attachments_for_run(run_id=456, limit=50)
attachments = api.attachments.get_attachments_for_plan(plan_id=10)
attachments = api.attachments.get_attachments_for_plan_entry(
    plan_id=10, entry_id=5
)
attachments = api.attachments.get_attachments_for_test(test_id=321)

# Download the raw bytes of an attachment (ID is int or UUID string)
data = api.attachments.get_attachment(attachment_id=443)
with open("downloaded.png", "wb") as f:
    f.write(data)

# Delete an attachment
api.attachments.delete_attachment(attachment_id=443)

Working with BDD Scenarios

# Import a BDD scenario
api.bdd.add_bdd(
    section_id=123,
    feature_file='path/to/feature/file.feature',
    description='Login feature tests'
)

# Export a BDD scenario
scenario = api.bdd.get_bdd(case_id=456)

Error Handling

The module includes comprehensive error handling with specific exception types:

from testrail_api_module import TestRailAPI, TestRailAPIError, TestRailAuthenticationError, TestRailRateLimitError

try:
    result = api.cases.get_case(case_id=999999)
    print(f"Case: {result['title']}")
except TestRailAuthenticationError as e:
    print(f"Authentication failed: {e}")
except TestRailRateLimitError as e:
    print(f"Rate limit exceeded: {e}")
except TestRailAPIError as e:
    print(f"API error: {e}")
except Exception as e:
    print(f"Unexpected error: {e}")

Exception Types

• TestRailAPIError: Base exception for all API-related errors
• TestRailAuthenticationError: Authentication failures (401 errors)
• TestRailRateLimitError: Rate limit exceeded (429 errors)
• TestRailAPIException: General API errors with status codes and response details

Historical migrations

Upgrading from an older version (e.g., v0.3.x's None-returning API or pre-v0.6.3 endpoint names)? See the CHANGELOG and GitHub releases for the breaking changes in each version.

Documentation

For complete documentation, visit our docs.

OpenAPI Specification

This repository ships a hand-authored OpenAPI 3.1 description of the TestRail v2 HTTP API at openapi/testrail.yaml. It covers every endpoint reachable from TestRailAPI.* (107 operations across 24 resource groups), including request bodies, query parameters, response schemas, the HTTP Basic auth scheme, the {offset, limit, size, _links, <entity>} pagination envelope, and error responses mapped to this package's exception hierarchy.

[!IMPORTANT] This spec is community-authored and is not produced or endorsed by Gurock / TestRail. Gurock has never published an official machine-readable contract for the TestRail API (the community request in gurock/testrail-api#6 has been open since 2017). This document is maintained here as a community resource and may lag behind, or diverge from, the behaviour of any particular TestRail server version. Always verify against your own instance for production use.

Per-instance custom fields (custom_* keys) cannot be enumerated statically, so the Case and Result schemas use additionalProperties: true; discover the live definitions at runtime via get_case_fields / get_result_fields. Operations whose exact response envelope has not been re-confirmed against a live instance are tagged x-verified: docs-only.

Validate the spec and check it for drift against the wrapper:

# Validates against the OpenAPI 3.1 meta-schema and asserts every wrapper
# endpoint has a matching spec path. Runs in CI on every push/PR.
uv run python openapi/check_spec.py

Dependency Management

This project uses modern Python packaging with pyproject.toml for dependency management.

Files

• pyproject.toml - Package configuration and dependency specifications

🔒 Security & Credential Protection

This project includes automated credential detection to prevent secrets from being committed to the repository.

Pre-commit Hooks

The repository uses pre-commit hooks that automatically:

• Detect secrets: Scans for API keys, passwords, tokens, private keys, and other credentials using detect-secrets
• Block commits: Prevents commits containing detected secrets
• Run on all git clients: Works with command line, GUI clients, and IDEs

Setting Up Pre-commit Hooks

1. Install dependencies:

   uv sync --extra dev
   

2. Install git hooks:

   pre-commit install
   

3. Run hooks manually (optional):

   pre-commit run --all-files
   

Credential Management Best Practices

✅ DO:

• Use environment variables for credentials (TESTRAIL_API_KEY, TESTRAIL_PASSWORD)
• Store credentials in .env files (already in .gitignore)
• Use GitHub Secrets for CI/CD pipelines
• Use test credentials in test files (they're excluded from secret detection)

❌ DON'T:

• Commit .env files or any files containing real credentials
• Hardcode API keys or passwords in source code
• Commit files with .key, .pem, or other credential file extensions
• Bypass pre-commit hooks with --no-verify when committing credentials

What Gets Detected

The secret detection scans for:

• API keys and tokens (TestRail, GitHub, AWS, etc.)
• Passwords and authentication credentials
• Private keys (SSH, SSL certificates)
• High-entropy strings (likely to be secrets)
• Common credential patterns

If You Accidentally Commit Credentials

If credentials are accidentally committed:

1. Immediately rotate/revoke the exposed credentials
2. Remove from git history using git filter-branch or BFG Repo-Cleaner
3. Force push to update the remote repository (coordinate with team)
4. Notify team members to update their local repositories

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Authors

• Matt Troutman
• Christian Thompson
• Andrew Tipper

Support

If you encounter any issues or have questions, please open an issue on GitHub.