test-and-fix

You are running tests and fixing any issues found. This command iteratively tests, diagnoses problems, fixes them, and retests.

Related Skills

• testing.md - Testing strategy details
• security.md - Security fix patterns

Overview

This command follows a test → diagnose → fix → retest loop until all tests pass or manual intervention is needed.

Step 1: Initial Test Run

echo "🧪 Running initial tests..."

# Determine project type and run appropriate tests
if [ -f "Anchor.toml" ]; then
    # Anchor project
    anchor build && anchor test --skip-deploy
    TEST_STATUS=$?
elif grep -q "solana-program" Cargo.toml 2>/dev/null; then
    # Native Solana program
    cargo build-sbf && cargo test
    TEST_STATUS=$?
else
    # Standard Rust or backend
    cargo test
    TEST_STATUS=$?
fi

if [ $TEST_STATUS -eq 0 ]; then
    echo "✅ All tests passed!"
    exit 0
fi

echo "❌ Tests failed. Starting diagnosis..."

Step 2: Diagnose Issues

Analyze the test output to categorize failures:

Common Issue Categories

1. Format Issues

   • Code not formatted
   • Inconsistent style

2. Clippy Warnings

   • Lints not satisfied
   • Potential bugs

3. Compilation Errors

   • Syntax errors
   • Type mismatches
   • Missing imports

4. Test Failures

   • Failed assertions
   • Logic errors
   • Account validation failures (Solana)

5. Runtime Errors

   • Panics
   • Arithmetic overflow
   • Account errors (Solana)

Step 3: Automatic Fixes

Fix Format Issues

# Always start with formatting
echo "📝 Fixing format issues..."
cargo fmt

# For TypeScript tests
if [ -d "tests" ] && ls tests/*.ts >/dev/null 2>&1; then
    npx prettier --write "tests/**/*.ts"
fi

echo "✅ Format fixed"

Fix Clippy Warnings (Auto-fixable)

echo "🔧 Fixing clippy warnings..."

# Apply automatic clippy fixes
cargo clippy --fix --allow-dirty --allow-staged

# Note: Not all clippy warnings are auto-fixable
# Manual fixes may be needed for:
# - Logic issues
# - Unsafe code
# - Complex refactorings

echo "✅ Clippy auto-fixes applied"