Skip to content

testing.md

Latest commit

 

History

History
112 lines (82 loc) · 2.99 KB

testing.md

File metadata and controls

112 lines (82 loc) · 2.99 KB

Testing

Test conventions, running the suite, and writing new tests.

Running Tests

# Ensure services are running
hexis up
hexis doctor

# Run all tests
POSTGRES_HOST=127.0.0.1 pytest tests -q

# Run specific test suites
pytest tests/db -q         # Database integration tests
pytest tests/core -q       # Core API tests
pytest tests/services -q   # Service-level tests
pytest tests/cli -q        # CLI smoke tests

Use POSTGRES_HOST=127.0.0.1 to avoid SSL negotiation flakes when connecting to the local Docker Postgres.

Test Organization

tests/
├── db/          # Database schema, functions, triggers
├── core/        # Core API and tool tests
├── services/    # Service orchestration tests
└── cli/         # CLI smoke tests

Conventions

Framework

  • pytest + pytest-asyncio with session loop scope
  • Integration tests using transactions/rollbacks

Async Tests

All async tests using the db_pool fixture must use loop_scope="session":

pytestmark = [pytest.mark.asyncio(loop_scope="session")]

Unique Test Data

Use get_test_identifier() from tests/utils.py for unique data:

from tests.utils import get_test_identifier

async def test_something(db_pool):
    identifier = get_test_identifier()
    # Use identifier for unique content

Seeding Memories

The memories table has a NOT NULL constraint on embedding. Use array_fill for dummy vectors:

await conn.fetchval("""
    INSERT INTO memories (type, content, embedding, importance, trust_level, status)
    VALUES ('semantic', $1, array_fill(0.1, ARRAY[embedding_dimension()])::vector, 0.8, 0.9, 'active')
    RETURNING id
""", content)

Naming

  • Functions: test_*
  • Files: test_*.py
  • Descriptive names that explain what's being tested

Test Coverage Areas

Area Priority Tests
Memory creation/retrieval High fast_recall, search_similar, create_*
Episodes and neighborhoods High Auto-assignment, staleness triggers
Concept hierarchy High link_memory_to_concept, ancestors
Graph operations Medium Edge types, SelfNode
Maintenance functions Medium Cleanup, neighborhood recomputation
Identity/worldview Medium Confidence updates, relationship edges
Views Low memory_health, cluster_insights
Indexes Low HNSW, GIN performance

Writing New Tests

  1. Place tests in the appropriate directory (tests/db/, tests/core/, etc.)
  2. Use the db_pool fixture for database access
  3. Use transactions with rollback for isolation
  4. Follow existing naming patterns
  5. Include both positive and negative test cases

Related