chore: remove uneeded module blocks

Author: weklund

test/unit/oauth/test_oauth_base_config_u.py

@@ -1,59 +1,3 @@
-"""
-Unit tests for OAuthConfig base class.
-
-The OAuthConfig class provides the abstract base class for OAuth configuration management
-across different OAuth protocol versions. This base class defines common attributes
-and methods for handling OAuth authentication lifecycle, including initialization,
-maintenance, and shutdown behaviors.
-
-Core Functionality Tested:
-==========================
-
-1. **Abstract Method Implementation**:
-   - Version method abstract enforcement
-   - Proper NotImplementedError raising for abstract methods
-
-2. **Configuration Management**:
-   - Default parameter initialization from environment variables
-   - Configuration copying with modifications
-   - Attribute validation during copy operations
-
-3. **Lifecycle Control**:
-   - OAuth initialization behavior configuration
-   - Brokerage session management settings
-   - OAuth maintenance and shutdown control
-
-Key Components:
-===============
-
-- **OAuthConfig**: Abstract base class for OAuth configuration
-- **Configuration Copying**: Deep configuration modification capabilities
-- **Environment Integration**: Default values from environment variables
-- **Abstract Method Pattern**: Enforced implementation in subclasses
-
-Test Coverage:
-==============
-
-This test suite focuses on the base class functionality that provides the foundation
-for OAuth protocol implementations:
-
-- **Abstract Method Validation**: Ensures subclass implementation requirements
-- **Configuration Copying**: Validates safe configuration modification patterns
-- **Attribute Management**: Tests proper attribute validation and assignment
-- **Default Behavior**: Verifies correct environment variable integration
-
-The tests ensure that the base class provides a solid foundation for OAuth protocol
-implementations while maintaining proper abstraction boundaries and validation.
-
-Security Considerations:
-========================
-
-The base class handles OAuth configuration parameters that form the foundation
-for secure authentication flows. Tests ensure proper validation without exposing
-sensitive configuration details or creating security vulnerabilities through
-improper configuration handling.
-"""
-
 import pytest
 
 from ibind.oauth import OAuthConfig

test/unit/oauth/test_oauth_config_u.py

@@ -1,75 +1,3 @@
-"""
-Unit tests for OAuth1aConfig.
-
-The OAuth1aConfig class provides configuration management for OAuth 1.0a authentication
-with Interactive Brokers (IBKR) API. This configuration class handles the validation
-and storage of all required parameters for establishing secure OAuth 1.0a connections
-including API endpoints, tokens, keys, and cryptographic key file paths.
-
-Core Functionality Tested:
-==========================
-
-1. **Configuration Initialization**:
-   - Default parameter initialization
-   - Custom parameter assignment
-   - Version identification for OAuth protocol
-
-2. **Configuration Validation**:
-   - Required parameter presence validation
-   - File path existence verification
-   - Comprehensive error reporting for missing components
-
-3. **Parameter Management**:
-   - OAuth endpoint URL configuration
-   - Access token and secret handling
-   - Consumer key and DH prime parameter storage
-   - Encryption and signature key file path management
-
-Key Components:
-===============
-
-- **OAuth1aConfig**: Main configuration class for OAuth 1.0a parameters
-- **Parameter Validation**: Required field checking and file existence verification
-- **Error Handling**: Descriptive error messages for configuration issues
-
-Required Parameters:
-===================
-
-The OAuth1aConfig requires the following parameters for proper operation:
-- oauth_rest_url: Base URL for OAuth REST API endpoints
-- live_session_token_endpoint: Endpoint path for live session token requests
-- access_token: OAuth access token for authenticated requests
-- access_token_secret: Secret associated with the access token
-- consumer_key: OAuth consumer key identifying the application
-- dh_prime: Diffie-Hellman prime parameter for key exchange
-- encryption_key_fp: File path to encryption private key
-- signature_key_fp: File path to signature private key
-
-Test Coverage:
-==============
-
-This test suite focuses on configuration validation logic that ensures:
-
-- **Parameter Completeness**: All required OAuth parameters are provided
-- **File System Validation**: Cryptographic key files exist and are accessible
-- **Error Reporting**: Clear, actionable error messages for configuration issues
-- **Version Compliance**: Correct OAuth protocol version identification
-
-The tests use temporary files to simulate real key file scenarios while avoiding
-dependencies on actual cryptographic key content or permanent file system state.
-
-Security Considerations:
-========================
-
-This configuration class handles sensitive authentication parameters including:
-- Access tokens and secrets
-- Consumer keys
-- File paths to private cryptographic keys
-
-Tests ensure proper validation without exposing sensitive values in error messages
-or test outputs, maintaining security best practices for credential handling.
-"""
-
 import tempfile
 import pytest
 from pathlib import Path

test/unit/support/test_logs_u.py

@@ -1,79 +1,3 @@
-"""
-Unit tests for logging utilities.
-
-The logs module provides centralized logging configuration and management for the ibind
-library. It handles console logging, file-based logging with daily rotation, and
-project-specific logger creation. The module supports environment-based configuration
-and ensures proper log formatting across all components.
-
-Core Functionality Tested:
-==========================
-
-1. **Project Logger Creation**:
-   - Logger naming based on file paths
-   - Default logger instantiation
-   - Logger hierarchy and namespace management
-
-2. **Logging System Initialization**:
-   - Console output configuration
-   - File-based logging setup
-   - Log level and format configuration
-   - Initialization state management and idempotency
-
-3. **Daily Rotating File Handler**:
-   - Automatic daily file rotation based on timestamps
-   - File path generation with date suffixes
-   - Directory creation for log files
-   - Stream management and file handle lifecycle
-
-4. **Configuration Management**:
-   - Environment variable integration
-   - Default value handling
-   - Runtime configuration override
-   - Logging behavior control flags
-
-Key Components:
-===============
-
-- **project_logger()**: Creates project-specific logger instances with proper naming
-- **ibind_logs_initialize()**: Configures the entire logging system with handlers and formatters
-- **new_daily_rotating_file_handler()**: Sets up file-based logging with daily rotation
-- **DailyRotatingFileHandler**: Custom logging handler for automatic daily file rotation
-
-Test Coverage:
-==============
-
-This test suite provides comprehensive coverage of logging functionality including:
-
-- **Logger Creation**: All project logger naming patterns and configurations
-- **Initialization Logic**: Complete system setup with various parameter combinations
-- **File Handling**: Daily rotation mechanics, file creation, and cleanup
-- **Error Conditions**: Invalid configurations, file system errors, and edge cases
-- **State Management**: Initialization tracking, global state handling, and reset scenarios
-
-The tests use extensive mocking to isolate logging components while maintaining
-realistic interaction patterns with the Python logging framework.
-
-Logging Behavior:
-=================
-
-The logging system supports multiple output modes:
-- Console-only logging for development
-- File-only logging for production
-- Combined console and file logging
-- Disabled logging for testing environments
-
-File logs use daily rotation with timestamps in filenames (e.g., `app__2024-01-15.txt`)
-and automatic directory creation for log storage locations.
-
-Security Considerations:
-========================
-
-Logging systems handle potentially sensitive information and file system access.
-Tests ensure proper handling of file permissions, directory traversal prevention,
-and safe handling of user-provided log file paths without exposing system internals.
-"""
-
 import datetime
 import logging
 import pytest