docs: Add README and logging to match python package

- The readme is useful for us during development. This should be eventually removed and replaced with gitbook docs.
This commit is contained in:
TAMARA LIPOWSKI
2025-09-03 00:16:32 -04:00
committed by Tamara
parent c89fbee0ae
commit c12affb3ca
6 changed files with 548 additions and 328 deletions

144
protocol-testing/README.md Normal file
View File

@@ -0,0 +1,144 @@
# Protocol Testing
Rust-based integration testing framework for Tycho protocol implementations.
## Prerequisites
1. **PostgreSQL Database**: Start the required PostgreSQL instance using Docker:
```bash
docker-compose up -d
```
2. **Environment Variables**: Source the environment variables:
```bash
source .env
```
Or set them manually:
- `DATABASE_URL`: PostgreSQL connection string (default: `postgres://postgres:mypassword@localhost:5431/tycho_indexer_0`)
- `RPC_URL`: Ethereum RPC endpoint
- `SUBSTREAMS_API_TOKEN`: Authentication token for Substreams API
- `AUTH_API_KEY`: API key for authentication
## Running Tests
### Basic Usage
```bash
cargo run -- --package <PACKAGE_NAME>
```
### Command Line Options
- `--package <NAME>` (required): Name of the package to test
- `--tycho-logs <BOOL>`: Enable tycho logs (default: true)
- `--db-url <URL>`: Postgres database URL (default: postgres://postgres:mypassword@localhost:5431/tycho_indexer_0)
- `--vm-traces <BOOL>`: Enable tracing during VM simulations (default: false)
### Examples
Run tests with default settings:
```bash
cargo run -- --package uniswap-v2
```
Run tests with VM tracing enabled:
```bash
cargo run -- --package uniswap-v2 --vm-traces true
```
Run tests with custom database URL:
```bash
cargo run -- --package uniswap-v2 --db-url postgres://user:pass@localhost:5432/custom_db
```
Run tests in silent mode (disable tycho logs):
```bash
cargo run -- --package uniswap-v2 --tycho-logs false
```
## Logging Configuration
The application uses `tracing` for structured logging. Control log levels using the `RUST_LOG` environment variable:
### Log Levels
```bash
# Show test results and progress (recommended)
export RUST_LOG=info
# Show all detailed logs including debug information
export RUST_LOG=debug
# Show only errors (silent mode)
export RUST_LOG=error
# Hide all logs (completely silent)
export RUST_LOG=warn
```
### Test Output Formatting
The test runner outputs results similar to:
```
Running 2 tests ...
--------------------------------
TEST 1: balancer_weighted_pool_test
✅ Protocol component validation passed.
✅ Token balance validation passed.
Amount out for 0x5c6ee304399dbdb9c8ef030ab642b10820db8f56000200000000000000000014: calculating for tokens "BAL"/"WETH"
Spot price "BAL"/"WETH": 0.123456
✅ Simulation validation passed.
✅ balancer_weighted_pool_test passed.
--------------------------------
Tests finished!
RESULTS: 2/2 passed.
```
### Module-specific Logging
```bash
# Enable debug logs for specific modules
export RUST_LOG=protocol_testing=debug,tycho_client=info
# Disable logs for noisy modules
export RUST_LOG=info,hyper=warn,reqwest=warn
```
### Running with Different Log Levels
```bash
# Standard test run with progress output
RUST_LOG=info cargo run -- --package uniswap-v2
# Detailed debug output
RUST_LOG=debug cargo run -- --package uniswap-v2
# Minimal output (errors only)
RUST_LOG=error cargo run -- --package uniswap-v2
```
## Test Configuration
Tests are configured via YAML files located in the substreams package directory:
- Test configuration: `../substreams/<package>/integration_test.tycho.yaml`
- Substreams configuration: `../substreams/<package>/substreams.yaml`
## What the Tests Do
1. **Component Validation**: Verifies that all expected protocol components are present in Tycho after indexing
2. **State Validation**: Compares indexed component states against expected values
3. **Balance Verification**: Validates token balances by querying the blockchain directly (can be skipped)
4. **Simulation Testing**: Runs Tycho simulation engine to verify protocol functionality
## Troubleshooting
- **Database Connection Issues**: Ensure PostgreSQL is running via `docker-compose up -d`
- **RPC Errors**: Verify `RPC_URL` is set and accessible
- **Missing Substreams**: Check that the package directory exists in `../substreams/<package>/`
- **Build Failures**: Ensure all dependencies are installed and environment variables are set