🧪 NeuroLink Testing Guide

May 8, 2026 · View on GitHub

🎉 Provider Testing Status

All 21+ providers confirmed working! OpenAI, Anthropic, Google AI, Google Vertex, AWS Bedrock, Azure OpenAI, Mistral, Hugging Face, Ollama, LiteLLM, AWS SageMaker, OpenAI-compatible, OpenRouter, DeepSeek, NVIDIA NIM, LM Studio, llama.cpp — plus voice (OpenAI TTS, ElevenLabs, Deepgram, Azure Speech, Google TTS/STT, Whisper, OpenAI Realtime, Gemini Live).

Quick Provider Validation

# Test any provider via the CLI
pnpm cli generate "test" --provider openai
pnpm cli generate "test" --provider anthropic
pnpm cli generate "test" --provider google-ai
pnpm cli generate "test" --provider deepseek
pnpm cli generate "test" --provider nvidia-nim
pnpm cli generate "test" --provider lm-studio
pnpm cli generate "test" --provider llamacpp
pnpm cli generate "test" --provider azure
pnpm cli generate "test" --provider mistral
pnpm cli generate "test" --provider ollama
pnpm cli generate "test" --provider vertex

# Test with enhancements (any provider works)
pnpm cli generate "test" --provider google-ai --enable-analytics --enable-evaluation --debug

Comprehensive Testing

# Run full validation suite
./validate-fixes.sh

# Run comprehensive CLI tests
node CLI_COMPREHENSIVE_TESTS.js

# Run before/after comparison
node BEFORE_AFTER_COMPARISON.js

Expected Results

CLI Enhancement Output:

📊 Analytics:
{
  "provider": "google-ai",
  "model": "gemini-2.5-pro",
  "tokens": {"input": 358, "output": 48, "total": 406},
  "responseTime": 1670,
  "context": {"test": "validation"}
}

⭐ Response Evaluation:
{
  "relevance": 7,
  "accuracy": 7,
  "completeness": 7,
  "overall": 7
}

SDK Enhancement Output:

// Result object contains:
{
  content: "AI response...",
  analytics: {
    provider: "google-ai",
    tokens: {input: 358, output: 48, total: 406},
    responseTime: 1670
  },
  evaluation: {
    overall: 7,
    relevance: 7,
    accuracy: 7,
    completeness: 7
  }
}

Provider Testing

Google AI Provider Validation

# Test working model
export GOOGLE_AI_MODEL=gemini-2.5-pro
node ./dist/cli/index.js generate "Hello" --provider google-ai --debug

# Expected: Real AI response with token counts
# Expected: No empty responses or fallbacks

OpenAI Provider Validation

# Test OpenAI fallback
node ./dist/cli/index.js generate "Hello" --provider openai --enable-analytics --debug

# Expected: OpenAI response with analytics data
# Expected: Accurate token counting (no NaN values)

Multi-Provider Testing

# Test provider auto-selection
node ./dist/cli/index.js generate "Hello" --enable-analytics --debug

# Expected: Best available provider selected automatically
# Expected: Graceful fallback if primary provider fails

Backward Compatibility Testing

Ensure No Breaking Changes

# Test existing CLI commands (no enhancement flags)
node ./dist/cli/index.js generate "Simple test"
node ./dist/cli/index.js generate "Simple test"
node ./dist/cli/index.js gen "Simple test"

# Expected: Normal AI responses
# Expected: No enhancement data displayed
# Expected: All existing functionality works

Test Existing SDK Integration

// Test basic SDK usage (no enhancements)
const { createBestAIProvider } = require("@juspay/neurolink");
const provider = createBestAIProvider();
const result = await provider.generate({ input: { text: "Hello" } });

// Expected: result.content contains AI response
// Expected: No analytics or evaluation fields
// Expected: Existing usage patterns continue working

Error Handling Testing

Invalid Model Names

# Test deprecated model handling
export GOOGLE_AI_MODEL=gemini-2.5-pro-preview-05-06
node ./dist/cli/index.js generate "test" --provider google-ai --debug

# Expected: Graceful fallback to working provider
# Expected: Clear error message or automatic correction

Missing API Keys

# Test without API keys
unset GOOGLE_AI_API_KEY
unset OPENAI_API_KEY
node ./dist/cli/index.js generate "test" --debug

# Expected: Clear error message about missing configuration
# Expected: Helpful setup instructions

Network Issues

# Test with invalid API endpoint (simulated)
node ./dist/cli/index.js generate "test" --timeout 5s --debug

# Expected: Timeout handled gracefully
# Expected: Fallback to other providers if available

Performance Testing

Response Time Validation

# Test response times with analytics
node ./dist/cli/index.js generate "Short prompt" --enable-analytics --debug

# Expected: responseTime field shows reasonable values (< 10s)
# Expected: Analytics data doesn't significantly slow requests

Token Counting Accuracy

# Test accurate token counting
node ./dist/cli/index.js generate "This is a test prompt for token counting" --enable-analytics --debug

# Expected: input + output = total tokens
# Expected: No NaN values in any token fields
# Expected: Token counts match actual usage

Enhancement Feature Validation

Analytics Data Completeness

# Test analytics data structure
node ./dist/cli/index.js generate "Business email" --enable-analytics --context '{"project":"test"}' --debug

# Expected analytics fields:
# - provider: string
# - model: string
# - tokens: {input, output, total}
# - responseTime: number
# - context: object (if provided)
# - timestamp: ISO string

Evaluation Data Validation

# Test evaluation scoring
node ./dist/cli/index.js generate "Explain quantum physics" --enable-evaluation --debug

# Expected evaluation fields:
# - relevance: number (1-10)
# - accuracy: number (1-10)
# - completeness: number (1-10)
# - overall: number (1-10)
# - evaluationModel: string
# - evaluationTime: number

Context Flow Testing

# Test context preservation
node ./dist/cli/index.js generate "Help with task" --context '{"userId":"123","department":"sales"}' --enable-analytics --debug

# Expected: Context object preserved in analytics.context
# Expected: Context available throughout request chain

Troubleshooting Guide

Common Issues

  1. Empty Responses from Google AI

    • Check model name in .env file
    • Use gemini-2.5-pro instead of deprecated models
    • Verify API key is valid

  2. NaN Token Counts

    • Usually indicates provider API failure
    • Check model configuration and API keys
    • Test with --debug flag for detailed logs

  3. Enhancement Data Missing

    • Ensure using --debug flag to see enhancement output
    • Verify enhancement flags are correctly specified
    • Check that provider is working (not falling back)

  4. CLI Commands Not Found

    • Run npm run build:cli to rebuild CLI
    • Check that dist/cli/index.js exists
    • Verify Node.js version compatibility

Debug Commands

# Comprehensive debug information
node ./dist/cli/index.js generate "debug test" --provider google-ai --enable-analytics --enable-evaluation --context '{"debug":true}' --debug

# Check provider status
node ./dist/cli/index.js status

# Test specific provider
node ./dist/cli/index.js generate "provider test" --provider openai --debug

Test Automation

Validation Script Usage

# Run complete validation suite
./validate-fixes.sh

# Run specific test categories
./validate-fixes.sh --cli-only
./validate-fixes.sh --sdk-only
./validate-fixes.sh --providers-only

CI/CD Integration

# Add to CI pipeline
npm run test
npm run build:cli
./validate-fixes.sh --ci-mode

This testing guide ensures all enhancement features work correctly while maintaining backward compatibility and providing clear troubleshooting guidance.