Integration Testing Issues#

Common issues and solutions for Gold Digger's integration testing framework.

Current Implementation Status#

The integration testing framework is actively under development. Some tests may be incomplete or marked as TODO. This is expected during the development phase.

Docker Not Available#

Symptom: Integration tests fail with "Docker not available" or similar errors.

Solution:

# Check Docker status
docker info

# Start Docker service (Linux)
sudo systemctl start docker

# Start Docker Desktop (macOS/Windows)
# Use Docker Desktop application

# Verify Docker is working
docker run hello-world

Container Startup Timeouts#

Symptom: Tests fail with container startup timeouts in CI environments.

Solution:

# Increase timeout for CI environments
export TESTCONTAINERS_WAIT_TIMEOUT=300

# Run tests with extended timeout
cargo test --features integration_tests -- --ignored

Port Conflicts#

Symptom: Tests fail with "port already in use" errors.

Solution:

# Check for conflicting processes
lsof -i :3306

# Kill conflicting MySQL/MariaDB processes
sudo pkill -f mysql
sudo pkill -f mariadb

# Use random ports (testcontainers default)
# No manual port configuration needed

Test Execution Issues#

Integration Tests Not Running#

Symptom: Integration tests are skipped or not executed.

Solution:

# Ensure integration_tests feature is enabled
cargo test --features integration_tests -- --ignored

# Check test discovery
cargo test --features integration_tests --list | grep -E "(integration|tls_variants|database_seeding)"

# Run specific integration tests
cargo test --features integration_tests --test tls_variants_test -- --ignored
cargo test --features integration_tests --test tls_integration -- --ignored
cargo test --features integration_tests --test database_seeding_test -- --ignored

# Check if Docker is available
docker info

TLS Variant Tests Not Working#

Symptom: TLS variant tests fail with configuration or connection errors.

Solution:

# Check TLS variant test specifically
cargo test test_mysql_tls_variant --test tls_variants_test -- --ignored --nocapture

# Verify TLS configuration validation
cargo test test_tls_container_config_methods --test tls_variants_test

# Check container creation
cargo test test_connection_url_generation --test tls_variants_test -- --ignored

# Enable verbose logging
RUST_LOG=debug cargo test --test tls_variants_test -- --ignored --nocapture

Test Data Issues#

Symptom: Tests fail due to missing or incorrect test data.

Solution:

# Verify test fixtures exist
ls tests/fixtures/

# Check schema and seed data
cat tests/fixtures/schema.sql
cat tests/fixtures/seed_data.sql

# Regenerate test data if needed
just test-integration --verbose

Memory Issues with Large Datasets#

Symptom: Tests fail with out-of-memory errors during large dataset testing.

Solution:

# Increase available memory for tests
export RUST_MIN_STACK=8388608

# Run tests with memory profiling
cargo test --features integration_tests --release -- --ignored

# Skip performance tests if memory-constrained
cargo test --features integration_tests -- --ignored --skip performance

TLS Certificate Issues#

Certificate Validation Failures#

Symptom: TLS tests fail with certificate validation errors.

Solution:

# Check TLS certificate fixtures
ls tests/fixtures/tls/

# Verify certificate format
openssl x509 -in tests/fixtures/tls/server.pem -text -noout

# Regenerate certificates if expired
# (Certificate generation scripts in tests/fixtures/tls/)

TLS Connection Failures#

Symptom: TLS integration tests fail to establish secure connections.

Solution:

# Test TLS configuration separately
cargo test --test tls_config_unit_tests

# Check rustls dependencies
cargo tree | grep rustls

# Verify no native-tls conflicts
! cargo tree | grep native-tls || echo "native-tls conflict detected"

CI Environment Issues#

GitHub Actions Failures#

Symptom: Integration tests pass locally but fail in GitHub Actions.

Solution:

# Test with act (local GitHub Actions simulation)
act -j test-integration

# Check CI-specific environment variables
env | grep CI
env | grep GITHUB

# Use CI-compatible timeouts
export CI=true
export GITHUB_ACTIONS=true

Resource Limits in CI#

Symptom: Tests fail due to CI resource constraints.

Solution:

# Use smaller test datasets in CI
if [ "$CI" = "true" ]; then
  export TEST_DATASET_SIZE=100
else
  export TEST_DATASET_SIZE=1000
fi

# Skip resource-intensive tests in CI
cargo test -- --ignored --skip large_dataset

Database-Specific Issues#

MySQL Version Compatibility#

Symptom: Tests fail with MySQL version-specific errors.

Solution:

# Check MySQL version in container
docker exec -it <container_id> mysql --version

# Use specific MySQL version
# (Configured in testcontainers setup)

# Test with multiple MySQL versions
cargo test --features integration_tests mysql_8_0 -- --ignored
cargo test --features integration_tests mysql_8_1 -- --ignored

MariaDB SSL Configuration#

Symptom: MariaDB TLS tests fail with SSL configuration errors.

Solution:

# Check MariaDB SSL status
docker exec -it <container_id> mysql -e "SHOW VARIABLES LIKE 'have_ssl';"

# Verify SSL certificate mounting
docker exec -it <container_id> ls -la /etc/mysql/ssl/

# Check MariaDB error log
docker logs <container_id>

Performance Issues#

Slow Test Execution#

Symptom: Integration tests take too long to complete.

Solution:

# Use nextest for parallel execution
cargo nextest run -- --ignored

# Run specific test categories
cargo test --test tls_variants_test -- --ignored
cargo test --test database_seeding_test -- --ignored

# Skip performance tests for faster feedback
cargo test -- --ignored --skip performance

Container Cleanup Issues#

Symptom: Containers not cleaned up after tests, consuming resources.

Solution:

# Enable Ryuk for automatic cleanup
export TESTCONTAINERS_RYUK_DISABLED=false

# Manual container cleanup
docker ps -a | grep testcontainers | awk '{print $1}' | xargs docker rm -f

# Clean up test networks
docker network prune -f

Debugging Integration Tests#

Verbose Test Output#

# Run with verbose output
RUST_LOG=debug cargo test --features integration_tests -- --ignored --nocapture

# Keep containers running for inspection
TESTCONTAINERS_RYUK_DISABLED=true cargo test --features integration_tests -- --ignored

# Run specific test files with verbose output
RUST_LOG=debug cargo test --features integration_tests --test tls_variants_test -- --ignored --nocapture
RUST_LOG=debug cargo test --features integration_tests --test database_seeding_test -- --ignored --nocapture

# Generate detailed test reports
cargo nextest run --features integration_tests --profile ci -- --ignored

Common TLS Issues#

Symptom: TLS tests fail with certificate or connection errors.

Solution:

# Check TLS certificate generation
cargo test test_tls_config_validation --test tls_variants_test

# Verify TLS container configuration
cargo test test_tls_container_config_methods --test tls_variants_test

# Test TLS connection validation
cargo test test_complete_tls_vs_plain_workflow --test tls_variants_test -- --ignored

# Check rustls dependencies
cargo tree | grep rustls

Container Inspection#

# List running containers
docker ps

# Inspect container configuration
docker inspect <container_id>

# Access container shell
docker exec -it <container_id> /bin/bash

# Check container logs
docker logs <container_id>

Test Coverage Analysis#

# Generate coverage for integration tests
cargo llvm-cov --features integration_tests --html -- --ignored

# Generate coverage for all tests
cargo llvm-cov --features integration_tests --html -- --include-ignored

# View coverage report
open target/llvm-cov/html/index.html

Getting Help#

If you encounter issues not covered here:

Check the logs: Enable verbose logging with RUST_LOG=debug
Verify Docker setup: Ensure Docker is running and accessible
Test isolation: Run individual tests to isolate issues
CI reproduction: Use act to reproduce CI failures locally
Create an issue: Report bugs with detailed error messages and environment information

For more information, see the Integration Testing Framework documentation.

Integration Testing Issues#

Current Implementation Status#

Docker-Related Issues#

Docker Not Available#

Container Startup Timeouts#

Port Conflicts#

Test Execution Issues#

Integration Tests Not Running#

TLS Variant Tests Not Working#

Test Data Issues#

Memory Issues with Large Datasets#

TLS Certificate Issues#

Certificate Validation Failures#

TLS Connection Failures#

CI Environment Issues#

GitHub Actions Failures#

Resource Limits in CI#

Database-Specific Issues#

MySQL Version Compatibility#

MariaDB SSL Configuration#

Performance Issues#

Slow Test Execution#

Container Cleanup Issues#

Debugging Integration Tests#

Verbose Test Output#

Common TLS Issues#

Container Inspection#

Test Coverage Analysis#

Getting Help#