validate

Files (1)

• SKILL.md

SKILL.md (first lines)

Run comprehensive validation of the project to ensure all tests, type checks, linting, and deployments are working correctly.

Execute the following commands in sequence and report results:

## 1. Test Suite

```bash
uv run pytest -v
```

**Expected:** All tests pass (currently 34 tests), execution time < 1 second

## 2. Type Checking

```bash
uv run mypy app/
```

**Expected:** "Success: no issues found in X source files"

```bash
uv run pyright app/
```

**Expected:** "0 errors, 0 warnings, 0 informations"

## 3. API Integration Tests

### Purpose
Verify external API integrations work correctly with real API calls.

### Prerequisites
- All required API keys configured in environment
- APIs must be accessible (network connectivity)
- Test accounts/projects exist in external services

### Validation Steps

#### 3.1 Configuration Validation
Check that all required API configuration is present:

```bash
# Check environment variables
env | grep -E "(API_KEY|API_TOKEN|LANGSMITH|OPENAI)"

# Verify config file (if applicable)
cat backend/.env | grep -E "^[A-Z_]*API"
```

**Expected:**
- All required API keys: SET (not empty)
- Configuration file readable and valid

**If Failed:**
- Error: Missing API keys
- Action: Check .env file, environment setup

#### 3.2 API Connectivity Tests
Test that each API is accessible and credentials work:

```bash
# LangSmith connectivity test
python -c "
from langsmith import Client
client = Client()
projects = list(client.list_projects(limit=1))
print(f'✓ LangSmith: {len(projects)} projects')
"

# OpenAI API test
python -c "
from openai import OpenAI
client = OpenAI()
models = client.models.list(limit=1)
print(f'✓ OpenAI: API accessible')
"
```

**Expected:**
- Each API returns successful response
- Credentials validated
- No authentication errors

**If Failed:**
- Error: Invalid API key / Unauthorized
- Action: Verify API key in dashboard, regenerate if needed

#### 3.3 API Response Format Verification
Verify API responses match expected format:

```bash
# Test actual API call and response structure
python -c "
# Test streaming response event types
# Test data structure
# Verify against documented schema
"
```

**Expected:**
- Response matches documented schema
- Event types match API documentation
- Data structure is parseable

**If Failed:**
- Error: Unexpected response format
- Action: Check API version, update integration code

#### 3.4 Integration Flow Test
Test complete integration flow end-to-end:

```bash
# Example: Create trace, verify it appears
# Example: Make API call, verify logging
# Example: Test error handling
```

**Expected:**
- Complete flow executes successfully

From giladresisi/ai-dev-env, MIT.

More from giladresisi/ai-dev-env