Files
aitbc 96088f4501
Some checks failed
API Endpoint Tests / test-api-endpoints (push) Successful in 46s
CLI Tests / test-cli (push) Failing after 2s
Documentation Validation / validate-docs (push) Failing after 9s
Documentation Validation / validate-policies-strict (push) Failing after 12s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 24s
Package Tests / Python package - aitbc-core (push) Successful in 19s
Package Tests / Python package - aitbc-crypto (push) Successful in 10s
Package Tests / Python package - aitbc-sdk (push) Successful in 16s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 5s
Package Tests / JavaScript package - aitbc-token (push) Successful in 10s
Production Tests / Production Integration Tests (push) Successful in 17s
Python Tests / test-python (push) Successful in 8s
Security Scanning / security-scan (push) Successful in 46s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 3s
Integration Tests / test-service-integration (push) Failing after 11m28s
docs-validation: expand curated markdown scope to include all documentation hubs
Add all documentation subdirectories to the curated markdown linting targets, replacing the previous exclusion-based approach with comprehensive coverage. Update validation to check for required README files across all hubs and verify priority documentation metadata markers. Implement lazy loading for optional dependencies (numpy, redis, bcrypt, jwt, websockets) in agent-coordinator and related modules to improve startup
2026-04-27 11:57:36 +02:00
..

AITBC Testing Documentation

Level: Intermediate
Prerequisites: Basic familiarity with the AITBC codebase, Python testing tools, and service management
Estimated Time: 20-40 minutes
Last Updated: 2026-04-27
Version: 1.0

🧭 Navigation Path:

🏠 Documentation Home🧪 TestingYou are here

breadcrumb: Home → Testing → Overview


🎯 See Also:


📚 What lives here

This directory contains the comprehensive test suite documentation for the AITBC platform. It covers unit tests, integration tests, end-to-end tests, security tests, and load tests.

Recent Updates (April 13, 2026)

Test Cleanup Completed

  • Archived Tests: Removed legacy archived tests directory (6 files)
  • Conftest Consolidation: Deleted duplicate conftest files, kept main conftest.py
  • Test Runner Cleanup: Deleted run_all_phase_tests.py (phase2 missing)
  • Phase Tests Archived: Moved phase3, phase4, phase5 to archived_phase_tests/
  • Active Tests: phase1, cross_phase, production, integration remain active

Previous Updates (March 30, 2026)

Structure Improvements Completed

  • Scripts Organization: Test scripts moved to scripts/testing/ and scripts/utils/
  • Logs Consolidation: All test logs now in /var/log/aitbc/
  • Virtual Environment: Using central /opt/aitbc/venv
  • Development Environment: Using /etc/aitbc/.env for configuration

📑 Table of Contents

  1. Test Structure
  2. Prerequisites
  3. Running Tests
  4. Test Types
  5. Configuration
  6. CI/CD Integration
  7. Troubleshooting

🧱 Test Structure

tests/
├── conftest.py                    # Main shared fixtures and configuration
├── run_production_tests.py        # Production test runner
├── load_test.py                   # Load testing utilities
├── docs/                          # Test documentation
│   ├── README.md
│   ├── USAGE_GUIDE.md
│   ├── TEST_REFACTORING_COMPLETED.md
│   ├── cli-test-updates-completed.md
│   └── test-integration-completed.md
├── archived_phase_tests/          # Archived legacy phase tests
│   ├── phase3/                    # Decision framework tests
│   ├── phase4/                    # Autonomous decision making tests
│   └── phase5/                    # Vision integration tests
├── phase1/                        # Phase 1 tests (active)
│   └── consensus/                # Consensus layer tests
├── cross_phase/                   # Cross-phase integration tests (active)
├── production/                    # Production test suite (active)
├── integration/                   # Integration tests (active)
├── fixtures/                      # Test fixtures and data
├── __pycache__/                   # Python cache (auto-generated)
└── __pycache__/                   # Python cache (auto-generated)
scripts/testing/           # Main testing scripts
├── comprehensive_e2e_test_fixed.py  # Comprehensive E2E testing
├── test_workflow.sh               # Workflow testing
├── run_all_tests.sh               # All tests runner
└── test-all-services.sh           # Service testing

scripts/utils/             # Testing utilities
├── requirements_migrator.py       # Dependency management
└── other utility scripts          # Various helper scripts

Prerequisites

Environment Setup

# Run main project setup (if not already done)
./setup.sh

# Activate central virtual environment
source /opt/aitbc/venv/bin/activate

# Ensure test dependencies are installed
pip install pytest pytest-cov pytest-asyncio

# Set environment configuration
source /etc/aitbc/.env  # Central environment configuration

Service Requirements

  • AITBC blockchain node running
  • Coordinator API service active
  • Database accessible (SQLite/PostgreSQL)
  • GPU services (if running AI tests)

▶️ Running Tests

Quick Start

# Run all fast tests
python tests/test_runner.py

# Run comprehensive test suite
python tests/test_runner.py --all

# Run with coverage
python tests/test_runner.py --coverage

Specific Test Types

# Unit tests only
python tests/test_runner.py --unit

# Integration tests only
python tests/test_runner.py --integration

# CLI tests only
python tests/test_runner.py --cli

# Performance tests
python tests/test_runner.py --performance

Advanced Testing

# Comprehensive E2E testing
python scripts/testing/comprehensive_e2e_test_fixed.py

# Workflow testing
bash scripts/testing/test_workflow.sh

# All services testing
bash scripts/testing/test-all-services.sh

🧪 Test Types

Unit Tests

  • Location: tests/unit/ (if exists)
  • Purpose: Test individual components in isolation
  • Speed: Fast (< 1 second per test)
  • Coverage: Core business logic

Integration Tests

  • Location: tests/integration/ and tests/e2e/
  • Purpose: Test component interactions
  • Speed: Medium (1-10 seconds per test)
  • Coverage: API endpoints, database operations

End-to-End Tests

  • Location: tests/e2e/ and scripts/testing/
  • Purpose: Test complete workflows
  • Speed: Slow (10-60 seconds per test)
  • Coverage: Full user scenarios

Performance Tests

  • Location: tests/load_test.py
  • Purpose: Test system performance under load
  • Speed: Variable (depends on test parameters)
  • Coverage: API response times, throughput

⚙️ Configuration

Test Configuration Files

  • pytest.ini: Pytest configuration (in root)
  • conftest.py: Shared fixtures and configuration
  • pyproject.toml: Project-wide test configuration

Environment Variables

# Test database (different from production)
TEST_DATABASE_URL=sqlite:///test_aitbc.db

# Test logging
TEST_LOG_LEVEL=DEBUG
TEST_LOG_FILE=/var/log/aitbc/test.log

# Test API endpoints
# Note: Port 8011 = Learning Service (updated port allocation)
TEST_API_BASE_URL=http://localhost:8011

🔄 CI/CD Integration

GitHub Actions

Test suite is integrated with CI/CD pipeline:

  • Unit Tests: Run on every push
  • Integration Tests: Run on pull requests
  • E2E Tests: Run on main branch
  • Performance Tests: Run nightly

Local CI Simulation

# Simulate CI pipeline locally
python tests/test_runner.py --all --coverage

# Generate coverage report
coverage html -o coverage_html/

🛠️ Troubleshooting

Common Issues

Test Failures Due to Services

# Check service status
systemctl status aitbc-blockchain-node
systemctl status aitbc-coordinator

# Restart services if needed
sudo systemctl restart aitbc-blockchain-node
sudo systemctl restart aitbc-coordinator

Environment Issues

# Check virtual environment
which python
python --version

# Check dependencies
pip list | grep pytest

# Reinstall if needed
pip install -e .

Database Issues

# Reset test database
rm test_aitbc.db
python -m alembic upgrade head

# Check database connectivity
python -c "from aitbc_core.db import engine; print(engine.url)"

Test Logs

All test logs are now centralized in /var/log/aitbc/:

  • test.log: General test output
  • test_results.txt: Test results summary
  • performance_test.log: Performance test results

Getting Help

  1. Check test logs in /var/log/aitbc/
  2. Review test documentation in tests/docs/
  3. Run tests with verbose output: pytest -v
  4. Check service status and configuration

📚 Further Reading:

🆘 Help & Support:


📊 Quality Metrics

  • Structure: 10/10 - Template-compliant landing page with detailed testing sections.
  • Content: 10/10 - Comprehensive test suite documentation with operational guidance.
  • Navigation: 10/10 - Links to docs home, CLI technical docs, deployment, and about docs.
  • Status: Active index page.

Last updated: 2026-04-27
Version: 1.0
Status: Active index for testing documentation