Testing Guide - MiTeddy Snipe Bot

⚠️ IMPORTANT: The RBF Bot (src/main-rbf.ts) is now the PRIMARY/PRODUCTION bot. The Original Bot (src/index.ts) is LEGACY/DEPRECATED.

🧪 Quick Test Checklist (RBF Bot)

Step 1: Configuration Verification (2 minutes)

# 1. Check .env file exists and has required values
# 2. Verify all required variables are set
# 3. Check contract address format
# 4. Verify RBF bot configuration (BASE_MULTIPLIER=200.0, RBF_* variables)

Step 2: Dry-Run Test (5 minutes)

npm run start:rbf:dry  # RBF bot (PRODUCTION)

Step 3: Ownership & Approval Test (10 minutes)

# Run without dry-run to test actual blockchain calls
npm run start:rbf  # RBF bot (PRODUCTION)
# (Stop with Ctrl+C after approvals are set)

Step 4: Full Integration Test (Wait for window)

# Run and wait for actual window to open
npm run start:rbf  # RBF bot (PRODUCTION)

Legacy Original Bot Testing [DEPRECATED]

npm run start:rbf:dry  # RBF bot (PRODUCTION)  # LEGACY - Original bot (not recommended)
npm start               # LEGACY - Original bot (not recommended)

📋 Detailed Testing Steps

Test 1: Configuration Validation

Purpose: Verify all config is correct before running

Steps:

Copy .env.example to .env
Fill in required values:
- PRIVATE_KEY - Your hot wallet private key
- SACRIFICE_ADDR - Contract address (validated automatically)
- TEDDY_ID - Your Steady Teddy token ID
- MIBERA_ID - Your Mibera token ID
Set optional values:
- UNLOCK_TIME_UNIT - seconds (default) or milliseconds

Expected Result:

✅ Bot starts without errors
✅ Shows wallet address
✅ Shows RPC count
✅ Shows token IDs
✅ Network verified (Chain ID 80094)

If Errors:

❌ "Missing required environment variable" → Check .env file
❌ "SACRIFICE_ADDR must be a valid Ethereum address" → Fix address format
❌ "Chain ID mismatch" → Check RPC endpoints

Test 2: Dry-Run Mode (RBF Bot)

Purpose: Test bot logic without sending transactions

Command:

npm run start:rbf:dry  # RBF bot (PRODUCTION)

What to Verify:

✅ Bot initializes successfully
✅ Network verification passes
✅ Ownership check runs (should pass if you own NFTs)
✅ Approval check runs (may set approval if needed)
✅ Bot enters polling loop
✅ View function checks work
✅ Logs show unlock time (if available)
✅ Dynamic polling activates when close to unlock
✅ NO transactions sent (dry-run mode)

Expected Output:

ℹ Initializing MiTeddy snipe bot...
ℹ Chain: Berachain (ID: 80094)
ℹ Wallet: 0x...
ℹ RPCs: 3 configured
✓ Network verified: Chain ID 80094
ℹ Verifying NFT ownership...
✓ Ownership verified - Steady Teddy #1234
✓ Ownership verified - Mibera #5678
ℹ Waiting for sacrifice window to open...
ℹ Polling every 250ms
ℹ Still waiting... (20 checks, unlock in ~45.2s)

Stop Test: Press Ctrl+C when satisfied

Test 3: Ownership Verification

Purpose: Verify bot correctly checks NFT ownership

Setup:

Use a wallet that owns both NFTs
Or use a wallet that doesn't own one (to test error handling)

Expected Behavior:

✅ If owns both: Continues to approval check
❌ If missing one: Shows clear error and exits

Error Example:

✗ You do not own Steady Teddy #1234. Owner: 0x...

Test 4: Approval Setting

Purpose: Verify bot sets approvals correctly

Setup:

Use wallet with NFTs but no approvals set

Expected Behavior:

✅ Checks if approval needed
✅ Sends setApprovalForAll transaction
✅ Waits for confirmation
✅ Continues to polling

In Dry-Run:

⚠️ Shows "DRY RUN: Would set approval"
✅ Doesn't actually send transaction

Test 5: View Function Caching

Purpose: Verify caching works correctly

What to Look For:

First call: Makes RPC call (slower)
Subsequent calls in same block: Uses cache (faster, no RPC call)
New block: Cache invalidates, fresh call

How to Verify:

Watch logs for RPC activity
Same block = no new RPC calls
New block = new RPC call

Test 6: Parallel Broadcasting

Purpose: Verify all RPCs receive transaction simultaneously

Setup:

Configure multiple RPCs in .env
Run in dry-run mode first

Expected Behavior:

✅ All RPCs receive transaction in parallel
✅ Logs show "Broadcast successful to RPC 1 (primary)", "RPC 2", etc.
✅ Faster than sequential broadcasting

In Dry-Run:

⚠️ Shows "DRY RUN: Would send transaction"
✅ Doesn't actually broadcast

Test 7: UnlockTime Unit Handling

Purpose: Verify unlockTime unit conversion works

Test Cases:

Case A: Contract Returns Seconds (Default)

# .env
UNLOCK_TIME_UNIT=seconds  # or omit (default)

Expected:

✅ Pre-warming triggers at 2 seconds (not 2000 seconds)
✅ Fast polling at < 1 second
✅ Logs show "Window opening in 2s" (not "2000ms")

Case B: Contract Returns Milliseconds

# .env
UNLOCK_TIME_UNIT=milliseconds

Expected:

✅ Pre-warming triggers at 2000ms (2 seconds)
✅ Fast polling at < 1000ms
✅ Logs show "Window opening in 2000ms"

How to Verify:

Check contract ABI/docs for remainingUnlockTime() return type
Set UNLOCK_TIME_UNIT accordingly
Watch logs when close to unlock
Verify timing matches expected behavior

Test 8: Dynamic Polling

Purpose: Verify polling speed adjusts based on unlock time

Expected Behavior:

Normal (> 5 seconds): Polls every SIMULATE_MS (default 250ms)
Close (< 5 seconds): Polls every 50ms
Very Close (< 1 second): Polls every 10ms

How to Verify:

Watch log timestamps
Should see faster polling as unlock time approaches
Logs should show "fast polling" or "increased polling"

Test 9: Pre-Warming

Purpose: Verify transaction pre-warming works

Setup:

Set PRE_WARM_TX=true in .env
Wait for unlock time < 2 seconds

Expected Behavior:

✅ Pre-warming triggers when < 2 seconds to unlock
✅ Only happens once (not repeatedly)
✅ Uses fresh nonce
✅ Pre-broadcasts to mempool
✅ Logs "Transaction pre-warmed to [private/public] mempool"

In Dry-Run:

⚠️ Pre-warming skipped (dry-run mode)

Test 10: RPC Health Check

Purpose: Verify RPC health monitoring works

Setup:

Set RPC_HEALTH_CHECK=true in .env
Configure multiple RPCs

Expected Behavior:

✅ Health check runs on startup
✅ RPCs sorted by latency
✅ Periodic health checks (every 100 attempts)
✅ Health checks skipped when < 10 seconds to unlock
✅ Logs show "RPCs sorted by latency: ..."

Test 11: Gas Bumping

Purpose: Verify gas bumping works (requires actual transaction)

Setup:

Run without dry-run
Use low gas price to force bumping

Expected Behavior:

✅ Sends transaction with initial gas
✅ If not included, bumps gas after BUMP_INTERVAL_MS
✅ Re-broadcasts with higher gas
✅ Continues up to MAX_BUMPS
✅ Logs show gas increases

Note: This test requires actual BERA for gas fees

Test 12: Error Handling

Purpose: Verify bot handles errors gracefully

Test Cases:

Case A: RPC Failure

Temporarily break one RPC URL
✅ Bot should continue with other RPCs
✅ Logs should show warnings

Case B: Network Issues

Disconnect internet briefly
✅ Bot should retry
✅ Logs should show errors

Case C: Invalid Configuration

Set invalid SACRIFICE_ADDR
✅ Should error clearly on startup
✅ Should not crash silently

🚀 Quick Start Testing

Minimal Test (2 minutes)

# 1. Set up .env with your values
# 2. Run dry-run
npm run start:rbf:dry  # RBF bot (PRODUCTION)

# 3. Verify:
# - Bot starts
# - Shows wallet
# - Enters polling loop
# - No errors

Full Test (10 minutes)

# 1. Set up .env
# 2. Run without dry-run
npm start

# 3. Verify:
# - Ownership check passes
# - Approvals set (if needed)
# - Polling works
# - View functions work
# - No crashes

# 4. Stop with Ctrl+C

🔍 What to Watch For

✅ Good Signs

Bot starts without errors
Network verification passes
Ownership verified
Polling loop runs smoothly
View function checks work
Logs show unlock time
Dynamic polling activates
No crashes or hangs

⚠️ Warning Signs

Errors in logs (check messages)
Bot hangs (check RPC connectivity)
Wrong unlock time (check UNLOCK_TIME_UNIT)
Memory usage growing (check cache limits)
Transactions not sending (check dry-run mode)

❌ Critical Issues

Bot crashes on startup → Check config
"Chain ID mismatch" → Check RPC endpoints
"You do not own..." → Check token IDs
"Invalid address" → Check SACRIFICE_ADDR format

📊 Testing Checklist

Pre-Production Checklist

🐛 Troubleshooting

Bot Won't Start

Check .env file exists and has all required variables
Check PRIVATE_KEY format (0x + 64 hex chars)
Check SACRIFICE_ADDR format (valid Ethereum address)
Check RPC URLs are accessible

Wrong Unlock Time

Verify contract's remainingUnlockTime() return type
Set UNLOCK_TIME_UNIT accordingly
Check logs for unlock time display

RPC Errors

Check RPC URLs are correct
Check network connectivity
Try different RPC providers
Check rate limits

Memory Issues

Check cache size limits (should be 1000 max)
Monitor memory usage over time
Restart bot periodically if needed

🎯 Recommended Test Sequence

Dry-Run (5 min) - Verify basic functionality
Ownership Test (2 min) - Verify NFT ownership check
Approval Test (5 min) - Verify approval setting
Extended Dry-Run (30 min) - Verify polling and caching
Full Test (Wait for window) - Verify complete flow

Ready to test! Start with dry-run mode for safest testing. 🚀

FilesExpand file tree

TESTING_GUIDE.md

Latest commit

History

TESTING_GUIDE.md

File metadata and controls

Testing Guide - MiTeddy Snipe Bot

🧪 Quick Test Checklist (RBF Bot)

Step 1: Configuration Verification (2 minutes)

Step 2: Dry-Run Test (5 minutes)

Step 3: Ownership & Approval Test (10 minutes)

Step 4: Full Integration Test (Wait for window)

Legacy Original Bot Testing [DEPRECATED]

📋 Detailed Testing Steps

Test 1: Configuration Validation

Test 2: Dry-Run Mode (RBF Bot)

Test 3: Ownership Verification

Test 4: Approval Setting

Test 5: View Function Caching

Test 6: Parallel Broadcasting

Test 7: UnlockTime Unit Handling

Case A: Contract Returns Seconds (Default)

Case B: Contract Returns Milliseconds

Test 8: Dynamic Polling

Test 9: Pre-Warming

Test 10: RPC Health Check

Test 11: Gas Bumping

Test 12: Error Handling

Case A: RPC Failure

Case B: Network Issues

Case C: Invalid Configuration

🚀 Quick Start Testing

Minimal Test (2 minutes)

Full Test (10 minutes)

🔍 What to Watch For

✅ Good Signs

⚠️ Warning Signs

❌ Critical Issues

📊 Testing Checklist

Pre-Production Checklist

🐛 Troubleshooting

Bot Won't Start

Wrong Unlock Time

RPC Errors

Memory Issues

🎯 Recommended Test Sequence