Testing

Overview

PROPPR includes integration tests to verify core functionality, including configuration loading, database connections, and service modules.

Test Structure

Tests are located in the tests/ directory at the PROPPR root:

PROPPR/
└── tests/
    ├── test_shared_services.py      # Config and module import tests
    ├── test_grading_functional.py   # Grading pipeline functional tests
    └── test_result_processor.py     # Result processing tests

Running Tests

Quick Test: Shared Services

Test configuration loading and module imports:

python tests/test_shared_services.py

What it tests:

Configuration imports from PROPPR.config
Credential loading from .env
SharedServices module imports
Grading system imports
MongoDB connection

Expected output:

============================================================
PROPPR SharedServices Migration Tests
============================================================

=== Testing Config Imports ===
✓ Config imports successful

=== Testing Credential Loading ===
  Environment: DEVELOPMENT
  MongoDB URI: mongodb+srv://...
  MongoDB Database: proppr
✓ Credentials loaded successfully

=== Testing SharedServices Config ===
  MONGO_DATABASE: proppr
  DEFAULT_GRADING_INTERVAL: 3600s
  BOT_CONFIGS keys: ['team', 'player']
  Player collection: all_positive_alerts
✓ SharedServices config imports successful

=== Testing Grading Module Imports ===
  ✓ UnifiedMarketMapper imported
  ✓ FotMobAPIService imported
  ✓ UnifiedResultProcessor imported
  ✓ UnifiedSheetsSync imported
  ✓ UnifiedGradingScheduler imported
✓ Grading module imports completed

=== Testing MongoDB Connection ===
  Connecting to proppr...
  ✓ MongoDB ping successful
  Collections found: 23
  Expected collections present: ['all_positive_alerts', 'all_positive_team_alerts']
✓ MongoDB connection successful

============================================================
Test Summary
============================================================
  Config Imports: ✓ PASS
  Credential Loading: ✓ PASS
  SharedServices Config: ✓ PASS
  Grading Imports: ✓ PASS
  MongoDB Connection: ✓ PASS

Total: 5/5 tests passed

Functional Tests: Grading Pipeline

Test the complete grading pipeline with real data:

python tests/test_grading_functional.py

What it tests:

Scheduler initialization with real config
Querying ungraded alerts from MongoDB
Alert grouping by fixture
FotMob API service
Market mapping functionality
Optional: Full grading cycle (interactive)

The grading cycle test can modify real data. It prompts for confirmation before running.

Expected output:

============================================================
PROPPR SharedServices Functional Tests
============================================================

=== Test: FotMob API Service ===
  Service initialized: True
  Base URL: https://www.fotmob.com/api
  Has turnstile cookies: True
  PASS: FotMob service initialized

=== Test: Market Mapper ===
    Goals (team): type_id=26, location=total
    Player Goals (player): type_id=95, location=total
    Corners (team): type_id=41, location=total
    Shots On Target (player): type_id=82, location=total
  PASS: Market mapper working

=== Test: Scheduler Initialization ===
  Bot type: team
  Config: {'collection': 'all_positive_team_alerts', 'spreadsheet': 'PROPPR Team Bot'}
  Grading interval: 3600s
  PASS: Scheduler initialized successfully

=== Test: Query Ungraded Alerts ===
  Found 42 ungraded alerts
  Sample alert:
    - Match: Arsenal vs Chelsea
    - Market: Goals Over 2.5
    - Date: 2026-03-04
    - fixture_id: 12345
  PASS: Query successful

=== Test: Alert Grouping ===
  Grouped 42 alerts into 8 fixtures
    - Fixture 12345: 6 alerts
    - Fixture 12346: 5 alerts
    - Fixture 12347: 8 alerts
  PASS: Grouping successful

=== Test: Grading Cycle (Dry Run) ===
  NOTE: This will attempt to grade real alerts if any exist
  Run grading test? (y/n): n
  SKIP: Grading test skipped by user

============================================================
Test Summary
============================================================
  FotMob Service: PASS
  Market Mapper: PASS
  Scheduler Init: PASS
  Query Alerts: PASS
  Alert Grouping: PASS
  Grading Cycle: SKIPPED

Total: 5 passed, 0 failed, 1 skipped

Test Categories

Configuration Tests

Verify environment and credential loading:

from PROPPR.config import (
    get_mongo_connection_string,
    get_mongo_database,
    get_telegram_token,
    is_production,
    is_development,
)

# Should not raise ImportError
assert callable(get_mongo_connection_string)
assert callable(is_production)

Import Tests

Verify all SharedServices modules can be imported:

# Market mapping
from PROPPR.SharedServices.mapping.market_mapper import UnifiedMarketMapper

# API services
from PROPPR.SharedServices.api.fotmob_service import FotMobAPIService

# Grading system
from PROPPR.SharedServices.grading.processors.result_processor import UnifiedResultProcessor
from PROPPR.SharedServices.grading.scheduler.unified_scheduler import UnifiedGradingScheduler

# Sheets sync
from PROPPR.SharedServices.sheets.sync.sync_service import UnifiedSheetsSync

Database Tests

Test MongoDB connection and collection access:

from PROPPR.config import get_mongo_connection_string, get_mongo_database
from pymongo import MongoClient

uri = get_mongo_connection_string()
db_name = get_mongo_database()

client = MongoClient(uri, serverSelectionTimeoutMS=5000)
client.admin.command('ping')  # Should not raise exception

db = client[db_name]
collections = db.list_collection_names()

assert 'all_positive_alerts' in collections
assert 'all_positive_team_alerts' in collections

client.close()

Integration Tests

Test complete workflows:

from PROPPR.SharedServices.grading.scheduler.unified_scheduler import UnifiedGradingScheduler
from PROPPR.config import get_mongo_connection_string, get_mongo_database

scheduler = UnifiedGradingScheduler(
    mongo_connection_string=get_mongo_connection_string(),
    database_name=get_mongo_database(),
    api_token="",
    credentials_path="credentials.json",
    spreadsheet_name="PROPPR Team Bot",
    bot_type='team'
)

# Query ungraded alerts
alerts = scheduler.result_processor.get_ungraded_alerts()
assert isinstance(alerts, list)

# Group by fixture
if alerts:
    grouped = scheduler.result_processor.group_alerts_by_fixture(alerts[:10])
    assert isinstance(grouped, dict)

scheduler.result_processor.close()

Manual Testing

Test Configuration Loading

Quickly verify your .env configuration:

python -c "
from PROPPR.config import (
    get_mongo_connection_string,
    get_mongo_database,
    get_telegram_token,
    is_development
)

print('=== Configuration Test ===')
print(f'Environment: {'Development' if is_development() else 'Production'}')
print(f'MongoDB URI: {get_mongo_connection_string()[:50]}...')
print(f'Database: {get_mongo_database()}')
print(f'Team Token: {get_telegram_token('team')[:20]}...' if get_telegram_token('team') else 'Team Token: Not set')
print('✓ All credentials loaded')
"

Test Market Mapping

Verify market normalization works correctly:

python -c "
from PROPPR.SharedServices.mapping.market_mapper import UnifiedMarketMapper

test_markets = [
    ('Goals', False),
    ('Player Goals', True),
    ('Corners', False),
    ('Shots On Target', True),
]

print('=== Market Mapping Test ===')
for market, is_player in test_markets:
    mapping = UnifiedMarketMapper.get_market_mapping(market, is_player)
    if mapping:
        print(f'{market}: type_id={mapping.get('type_id')}, location={mapping.get('location')}')
    else:
        print(f'{market}: No mapping')
"

Test Database Query

Verify you can query MongoDB collections:

python -c "
from PROPPR.config import get_mongo_connection_string, get_mongo_database
from pymongo import MongoClient

uri = get_mongo_connection_string()
db_name = get_mongo_database()

client = MongoClient(uri)
db = client[db_name]

print('=== Database Query Test ===')
print(f'Connected to: {db_name}')

# Count documents in key collections
for collection in ['all_positive_alerts', 'all_positive_team_alerts']:
    if collection in db.list_collection_names():
        count = db[collection].count_documents({})
        print(f'{collection}: {count} documents')
    else:
        print(f'{collection}: Not found')

client.close()
print('✓ Database query successful')
"

Test Data Requirements

MongoDB Collections

Tests expect these collections to exist:

all_positive_alerts - Player market alerts
all_positive_team_alerts - Team market alerts
game_info - Match information and results

If collections don’t exist, the tests will still run but may report zero alerts found. Run the data services (UnifiedAPIPoller, WebsocketUpdater) to populate data.

Environment Variables

Tests require these environment variables in .env:

MONGODB_URI_DEVELOPMENT="mongodb://..."
MONGODB_DATABASE="proppr"

Optional for full grading tests:

FOOTYSTATS_API_KEY="..."
GOOGLE_SHEET_ID_TEAM="..."

Continuous Integration

While PROPPR doesn’t currently use automated CI, you can set up basic checks:

Install dependencies

pip install -r requirements.txt

Run import tests

python tests/test_shared_services.py

Verify exit code

Tests exit with code 0 on success, 1 on failure:

python tests/test_shared_services.py && echo "Tests passed"

Common Test Failures

MongoDB connection failed

Cause: MongoDB not running or connection string incorrect.Solution:

Check MongoDB is running: mongosh
Verify .env has correct MONGODB_URI_DEVELOPMENT
If using Atlas, check IP whitelist

Config import failed

Cause: Python can’t find PROPPR module.Solution:

Run tests from PROPPR parent directory:

cd /path/to/Cerebro
python PROPPR/tests/test_shared_services.py

Credentials missing or empty

Cause: Required environment variables not set.Solution:

Check .env exists in PROPPR root
Verify required variables are set:
```
cat .env | grep MONGODB
```
See Local Setup

FotMob service import issue

Cause: FotMob service depends on turnstile cookies.Solution:

This is a warning, not a failure
Service will still initialize, but may have limited functionality
To fix, ensure turnstile_cookies.json exists in PROPPR root

Writing New Tests

Test Template

Use this template for new integration tests:

test_example.py

#!/usr/bin/env python3
"""
Test script for [feature name]
Verifies [what it tests]
"""

import sys
from pathlib import Path

# Ensure PROPPR parent is in path
proppr_parent = Path(__file__).resolve().parent.parent.parent
if str(proppr_parent) not in sys.path:
    sys.path.insert(0, str(proppr_parent))

def test_feature():
    """Test specific feature"""
    print("\n=== Testing Feature ===")
    try:
        # Your test code here
        print("✓ Test passed")
        return True
    except Exception as e:
        print(f"✗ Test failed: {e}")
        import traceback
        traceback.print_exc()
        return False

def main():
    """Run all tests"""
    print("=" * 60)
    print("Test Suite Name")
    print("=" * 60)
    
    results = []
    results.append(("Feature Test", test_feature()))
    
    # Summary
    print("\n" + "=" * 60)
    print("Test Summary")
    print("=" * 60)
    
    passed = sum(1 for _, r in results if r)
    total = len(results)
    
    for name, result in results:
        status = "✓ PASS" if result else "✗ FAIL"
        print(f"  {name}: {status}")
    
    print(f"\nTotal: {passed}/{total} tests passed")
    return passed == total

if __name__ == '__main__':
    success = main()
    sys.exit(0 if success else 1)

Best Practices

Always set up Python path correctly for imports

Handle exceptions and print detailed error messages

Return boolean success/failure for each test

Exit with appropriate exit codes (0 = success, 1 = failure)

Print clear test progress and summary

Next Steps

Local Setup

Set up your development environment

Running Locally

Learn how to run services locally

Get started

Services

Alert bots

Data services

Shared services

Configuration

Deployment

Development

Overview

Test Structure

Running Tests

Quick Test: Shared Services

Functional Tests: Grading Pipeline

Test Categories

Configuration Tests

Import Tests

Database Tests

Integration Tests

Manual Testing

Test Configuration Loading

Test Market Mapping

Test Database Query

Test Data Requirements

MongoDB Collections

Environment Variables

Continuous Integration

Common Test Failures

Writing New Tests

Test Template

Best Practices

Next Steps

Local Setup

Running Locally

Build docs developers (and LLMs) love

Get started

Services

Alert bots

Data services

Shared services

Configuration

Deployment

Development

​Overview

​Test Structure

​Running Tests

​Quick Test: Shared Services

​Functional Tests: Grading Pipeline

​Test Categories

​Configuration Tests

​Import Tests

​Database Tests

​Integration Tests

​Manual Testing

​Test Configuration Loading

​Test Market Mapping

​Test Database Query

​Test Data Requirements

​MongoDB Collections

​Environment Variables

​Continuous Integration

​Common Test Failures

​Writing New Tests

​Test Template

​Best Practices

​Next Steps

Local Setup

Running Locally

Build docs developers (and LLMs) love

Overview

Test Structure

Running Tests

Quick Test: Shared Services

Functional Tests: Grading Pipeline

Test Categories

Configuration Tests

Import Tests

Database Tests

Integration Tests

Manual Testing

Test Configuration Loading

Test Market Mapping

Test Database Query

Test Data Requirements

MongoDB Collections

Environment Variables

Continuous Integration

Common Test Failures

Writing New Tests

Test Template

Best Practices

Next Steps