c6054218c8
**Issue**: 21 E2E tests failing with InvalidSignature JWT errors **Root Cause #1**: Asymmetric whitespace trimming in JWT secret loading **Root Cause #2**: Missing backtests database schema ## Fixes Applied ### Agent 411: JWT Whitespace Trimming - **File**: services/api_gateway/src/auth/jwt/service.rs:128 - **Problem**: Secrets from files trimmed, env vars not trimmed - **Fix**: Added `.trim().to_string()` to env var loading path - **Impact**: Consistent secret handling across load methods ### Agent 412: Database Schema Creation - **File**: services/backtesting_service/migrations/001_create_tables_fixed.sql - **Problem**: backtests table didn't exist (syntax errors in original migration) - **Fix**: Created 8 tables + 28 indexes for backtesting service - **Impact**: +1 test passing (test_e2e_backtest_list) ## Test Results - Before: 28/49 (57.1%) - After Phase 1-2: 29/49 (59.2%) - Improvement: +1 test (+2.1%) ## Files Modified - services/api_gateway/src/auth/jwt/service.rs (+2 lines) - services/backtesting_service/migrations/001_create_tables_fixed.sql (new file, 8 tables, 28 indexes) Co-authored-by: Wave 149 Agent 411 (JWT Whitespace) Co-authored-by: Wave 149 Agent 412 (Database Schema)
Backtesting Service
Overview
The backtesting_service offers an independent and isolated environment for rigorously testing and validating trading strategies against historical market data. It provides a robust platform for simulating trading performance, analyzing strategy efficacy, and generating comprehensive performance reports before live deployment.
Features
- Independent Backtesting Service: Operates autonomously, allowing for parallel and isolated strategy evaluations.
- gRPC API for Backtest Execution: Exposes a clear API for submitting and managing backtesting jobs.
- Strategy Testing and Validation: Enables comprehensive testing of various trading strategies under different market conditions.
- Performance Reporting: Generates detailed reports including metrics like P&L, Sharpe ratio, drawdown, and win rate.
- Data Replay Engine: Accurately replays historical market data, simulating real-world order book dynamics and trade execution.
- Results Persistence: Stores backtesting results and reports for historical analysis and comparison.
gRPC API
The backtesting_service exposes a gRPC API for initiating and retrieving backtest results. Key endpoints include:
RunBacktest- Submit backtest configuration and strategyGetBacktestResults- Retrieve results for completed backtestsListAvailableStrategies- List registered strategiesGetBacktestReport- Get detailed performance report
Running the service
To run the backtesting_service binary:
cargo run --bin backtesting_service
Data Requirements
The service requires historical market data in Parquet format:
- Data should be stored in the configured data directory
- Supports tick data, order book snapshots, and OHLCV candles
- Data must include instrument, timestamp, and price/quantity fields
Testing
To run the tests for the backtesting_service crate:
cargo test --package backtesting_service
Documentation
Comprehensive API documentation is available at docs.rs/backtesting_service.