Running Tests

Prerequisites

Before running any tests, ensure you have the following installed:

• Python 3.12 via pyenv (pinned in .python-version at repo root)
• Poetry for dependency management
• Docker and Docker Compose (required for flaring-monitor integration tests and the full integration test script)

Per-Service Test Commands

Each Python service has its own test suite. Navigate to the service directory and run pytest through Poetry:

# General pattern
cd services/{service-name}
poetry install       # Install dependencies (first time or after changes)
poetry run pytest    # Run all tests
 
# With verbose output
poetry run pytest -v
 
# Run a specific test file
poetry run pytest tests/test_api.py
 
# Run a specific test class or method
poetry run pytest tests/test_api.py::TestCreateApproval::test_create_named_individual

Quick Reference

Pytest Configuration

All services share the same pytest configuration in their pyproject.toml:

[tool.pytest.ini_options]
asyncio_mode = "auto"

This single setting enables automatic handling of async def test_* functions without needing @pytest.mark.asyncio decorators. There is no separate pytest.ini or setup.cfg — all configuration lives in pyproject.toml.

Running All Service Tests

To run tests across all services in sequence:

# From the repo root
for svc in memory-service approval-service auth-service ingestion-service \
           compliance-monitor flaring-monitor knowledge-graph-service \
           orchestration-engine; do
    echo "=== Testing $svc ==="
    (cd "services/$svc" && poetry run pytest -v) || echo "FAILED: $svc"
done

Integration Test Runner

The full end-to-end integration test is at infrastructure/scripts/integration-test.sh. It tests the entire AEGIS platform pipeline from data ingestion through agent execution to HITL approval.

Prerequisites for Integration Tests

All services must be running:

# Start all infrastructure and services
./infrastructure/scripts/start-all.sh

This boots Docker infrastructure (PostgreSQL, Redis, Kafka), all 8 Python services, and the Go API gateway.

Running the Integration Test

./infrastructure/scripts/integration-test.sh

What the Integration Test Covers

The script runs 7 sequential steps, each with pass/fail verification:

The script authenticates with AEGIS_TEST_EMAIL / AEGIS_TEST_PASSWORD (defaulting to admin@aegis.local / aegis-dev-admin) and uses color-coded output for pass/fail results.

Interpreting Results

─── Step 1: Health checks ───
✓ PASS: http://localhost:8001 healthy
✓ PASS: http://localhost:8002 healthy
...
═══════════════════════════════════════════════════
  AEGIS Integration Test — ALL STEPS PASSED
═══════════════════════════════════════════════════

If any step fails, the script exits immediately with a FAIL message indicating which service or assertion failed.

Useful Pytest Flags

# Show print output and logging
poetry run pytest -s
 
# Run only tests matching a keyword
poetry run pytest -k "test_create"
 
# Stop at first failure
poetry run pytest -x
 
# Run with coverage (if coverage is installed)
poetry run pytest --cov=memory --cov-report=term-missing
 
# Show the slowest 10 tests
poetry run pytest --durations=10

Troubleshooting Test Failures

”Module not found” errors

Make sure you have installed the service’s dependencies, including the shared library:

cd services/{service-name}
poetry install

The shared library (aegis-shared) is installed as a path dependency pointing to ../../shared. If shared models have changed, re-run poetry install in the service directory.

Async test not running

If an async test appears to be skipped or not discovered, verify that asyncio_mode = "auto" is set in the service’s pyproject.toml under [tool.pytest.ini_options].

Flaring monitor tests fail with connection errors

The flaring-monitor integration tests require a live PostgreSQL database:

# Start just PostgreSQL
docker compose up -d postgres
 
# Verify it is healthy
docker compose ps postgres

Import errors in conftest.py

Some conftest files import from the service source package (e.g., from memory.working import WorkingMemory). This requires the Poetry virtual environment to be active. Always run tests via poetry run pytest, not bare pytest.