iris-devtester 1.2.1

Battle-tested InterSystems IRIS infrastructure utilities for Python development

IRIS DevTools

Battle-tested InterSystems IRIS infrastructure utilities for Python development

What is This?

IRIS DevTools is a comprehensive Python package that provides automatic, reliable, production-tested infrastructure for InterSystems IRIS development. Born from years of production experience and hundreds of hours debugging IRIS + Docker + Python integration issues, this library codifies all the hard-won lessons into a reusable package.

The Problem It Solves

Ever experienced these?

• ❌ "Password change required" errors breaking your tests
• ❌ Port conflicts when running tests in parallel
• ❌ Tests polluting each other's data
• ❌ "Works on my machine" but fails in CI
• ❌ Spending hours debugging IRIS connection issues
• ❌ Copying infrastructure code between projects

IRIS DevTools fixes all of these automatically.

Quick Start

Installation

# Basic installation
pip install iris-devtester

# With DBAPI support (recommended - 3x faster)
pip install iris-devtester[dbapi]

# With all features
pip install iris-devtester[all]

Zero-Config Usage

from iris_devtools.containers import IRISContainer

# That's it! No configuration needed.
with IRISContainer.community() as iris:
    conn = iris.get_connection()
    cursor = conn.cursor()
    cursor.execute("SELECT $ZVERSION")
    print(cursor.fetchone())

Pytest Integration

# conftest.py
from iris_devtools.testing import iris_test_fixture
import pytest

@pytest.fixture(scope="module")
def iris_db():
    return iris_test_fixture()

# test_example.py
def test_my_feature(iris_db):
    conn, state = iris_db
    cursor = conn.cursor()
    cursor.execute("SELECT 1")
    assert cursor.fetchone()[0] == 1

Run tests:

pytest  # Just works! 🎉

Key Features

🔐 Automatic Password Management

• Detects "Password change required" errors
• Automatically resets passwords via Docker
• Transparent retry - your code never knows it happened

🐳 Testcontainers Integration

• Each test suite gets isolated IRIS instance
• Automatic cleanup (even on crashes)
• No port conflicts
• No test data pollution

🐋 Docker-Compose Support (NEW in v1.0.1)

• Attach to existing IRIS containers without lifecycle management
• Works with licensed IRIS via docker-compose
• CLI commands for quick operations (status, enable-callin, test-connection)
• Standalone utilities for shell scripts and automation
• Auto-discovery of container ports

⚡ DBAPI-First Performance

• Automatically uses fastest connection method
• DBAPI (Database API): 3x faster than JDBC (Java Database Connectivity)
• Falls back to JDBC if DBAPI unavailable
• All transparent to your code

📦 DAT Fixture Management

• Create reproducible test fixtures from IRIS tables
• 10-100x faster than programmatic data creation
• SHA256 checksum validation for data integrity
• Load 10K rows in <10 seconds
• CLI commands for create, load, validate

📊 Performance Monitoring

• Auto-configure ^SystemPerformance monitoring
• Task Manager integration for scheduled monitoring
• Resource-aware auto-disable under high load
• Automatic re-enable when resources recover
• Zero-config monitoring setup

🧪 Production-Ready Testing

• Schema validation & auto-reset
• Test data isolation
• Pre-flight checks
• Medical-grade reliability (94%+ coverage)

📦 Zero Configuration

• Sensible defaults
• Auto-discovery of IRIS instances
• Environment variable overrides
• Works with both Community & Enterprise editions

Example: Enterprise Setup

from iris_devtools.containers import IRISContainer

# Auto-discovers license from ~/.iris/iris.key
with IRISContainer.enterprise(namespace="PRODUCTION") as iris:
    conn = iris.get_connection()
    # Use your enterprise IRIS instance

Example: DAT Fixtures

Create reproducible test fixtures 10-100x faster than programmatic data creation:

from iris_devtools.fixtures import FixtureCreator, DATFixtureLoader

# Create fixture from existing data
creator = FixtureCreator()
manifest = creator.create_fixture(
    fixture_id="test-users-100",
    namespace="USER",
    output_dir="./fixtures/test-users-100"
)

# Load fixture in tests (10K rows in <10 seconds)
loader = DATFixtureLoader()
result = loader.load_fixture("./fixtures/test-users-100")
print(f"Loaded {len(result.tables_loaded)} tables in {result.elapsed_seconds:.2f}s")

CLI Usage

# Create fixture
iris-devtester fixture create --name test-100 --namespace USER --output ./fixtures/test-100

# Validate integrity
iris-devtester fixture validate --fixture ./fixtures/test-100

# Load fixture
iris-devtester fixture load --fixture ./fixtures/test-100

Example: Performance Monitoring

Auto-configure IRIS performance monitoring with resource-aware auto-disable:

from iris_devtools.containers.monitoring import configure_monitoring
from iris_devtools.containers import IRISContainer

with IRISContainer.community() as iris:
    conn = iris.get_connection()

    # Zero-config monitoring setup
    success, message = configure_monitoring(conn)
    print(f"Monitoring configured: {message}")

    # Automatically disables monitoring if CPU > 90%
    # Automatically re-enables when CPU < 85%

Example: Docker-Compose Integration (NEW in v1.0.1)

Work with existing IRIS containers (docker-compose, licensed IRIS, external containers):

from iris_devtools.containers import IRISContainer
from iris_devtools.utils import enable_callin_service, test_connection, get_container_status

# Approach 1: Attach to existing container
iris = IRISContainer.attach("iris_db")  # Your docker-compose service name
conn = iris.get_connection()  # Auto-enables CallIn, discovers port
cursor = conn.cursor()
cursor.execute("SELECT $ZVERSION")

# Approach 2: Standalone utilities (shell-friendly)
success, msg = enable_callin_service("iris_db")
success, msg = test_connection("iris_db", namespace="USER")
success, report = get_container_status("iris_db")

CLI Usage

# Check container status (aggregates running, health, connection)
iris-devtester container status iris_db

# Enable CallIn service (required for DBAPI connections)
iris-devtester container enable-callin iris_db

# Test database connection
iris-devtester container test-connection iris_db --namespace USER

# Reset password if needed
iris-devtester container reset-password iris_db --user _SYSTEM --password SYS

Docker-Compose Example

# docker-compose.yml
version: '3.8'
services:
  iris_db:
    image: intersystemsdc/iris:latest  # Licensed IRIS
    container_name: iris_db
    ports:
      - "1972:1972"
      - "52773:52773"

Then use iris-devtester with your existing container:

# No testcontainers overhead - use existing container
iris = IRISContainer.attach("iris_db")
conn = iris.get_connection()

See examples/10_docker_compose_integration.py for complete examples.

Architecture

Built on proven foundations:

• testcontainers-python: Industry-standard container management
• testcontainers-iris-python (caretdev): IRIS-specific extensions
• Battle-tested code: Extracted from production RAG (Retrieval-Augmented Generation) systems

Constitution

This library follows 8 core principles learned through production experience:

1. Automatic Remediation Over Manual Intervention - No "run this command" errors
2. DBAPI First, JDBC Fallback - Always use the fastest option
3. Isolation by Default - Each test gets its own database
4. Zero Configuration Viable - pip install && pytest just works
5. Fail Fast with Guidance - Clear errors with fix instructions
6. Enterprise Ready, Community Friendly - Both editions supported
7. Medical-Grade Reliability - 95%+ test coverage, all error paths tested
8. Document the Blind Alleys - Learn from our mistakes

Documentation

• Troubleshooting Guide
• Codified Learnings - Our hard-won knowledge
• Examples - Runnable code samples

Real-World Use Cases

Use Case 1: CI/CD (Continuous Integration/Continuous Deployment) Testing

# .github/workflows/test.yml
- name: Run tests
  run: |
    pip install iris-devtester[all]
    pytest  # IRIS spins up automatically!

Use Case 2: Local Development

# Start coding immediately - no setup!
from iris_devtools.connections import get_iris_connection

conn = get_iris_connection()  # Auto-discovers or starts container
# Code your features...

Use Case 3: Enterprise Production Testing

# Test against real enterprise features
with IRISContainer.enterprise(
    license_key="/path/to/iris.key",
    image="containers.intersystems.com/intersystems/iris:latest"
) as iris:
    # Test mirrors, sharding, etc.

Performance

Benchmarks on MacBook Pro M1:

• Container startup: ~5 seconds
• DBAPI connection: ~80ms
• JDBC connection: ~250ms
• Schema reset: <5 seconds
• Test isolation overhead: <100ms per test class

Requirements

• Python 3.9+
• Docker (for testcontainers)
• InterSystems IRIS (Community or Enterprise)

AI-Assisted Development

This project is optimized for AI coding assistants:

• AGENTS.md - Vendor-neutral AI configuration (build commands, CI/CD)
• CLAUDE.md - Claude Code-specific context and patterns
• .cursorrules - Cursor IDE configuration
• Comprehensive examples - All examples include expected outputs
• Structured documentation - Clear architecture, conventions, and troubleshooting

Contributing

We welcome contributions! This library embodies real production experience. If you've solved an IRIS infrastructure problem, please contribute it so others don't repeat the same journey.

See CONTRIBUTING.md for guidelines.

Credits

Built on the shoulders of giants:

• caretdev/testcontainers-iris-python - IRIS testcontainers foundation
• testcontainers/testcontainers-python - Container lifecycle management
• InterSystems - IRIS database platform

Special thanks to all the developers who debugged these issues so you don't have to.

License

MIT License - See LICENSE

Support

• GitHub Issues
• Documentation
• Stack Overflow (tag: intersystems-iris)

---

Remember: Every feature here was paid for with real debugging time. Use this library to stand on our shoulders, not repeat our mistakes. 🚀