القائمة
Executes comprehensive test suite across unit, integration, E2E, database, protocols, and intelligence algorithms
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | run-full-test-suite |
| description | Executes comprehensive test suite across unit, integration, E2E, database, protocols, and intelligence algorithms |
| user-invocable | true |
Executes comprehensive test suite across all categories: unit, integration, E2E, database, protocols, and intelligence algorithms.
Run this skill:
# Run ALL tests (unit + integration + doc tests)
cargo test --all-features
# Run the full CI validation suite
./scripts/ci/lint-and-test.sh
# All library unit tests
cargo test --lib -- --quiet
# All integration tests
cargo test --test '*' -- --quiet
# Specific integration test
cargo test --test mcp_multitenant_complete_test -- --nocapture
# Documentation example tests
cargo test --doc -- --quiet
# Basic intelligence algorithms
cargo test --test intelligence_tools_basic_test -- --nocapture
# Advanced intelligence algorithms
cargo test --test intelligence_tools_advanced_test -- --nocapture
# MCP protocol tests
cargo test protocol -- --quiet
# OAuth tests
cargo test oauth -- --quiet
# Authentication tests
cargo test auth -- --quiet
# Database abstraction layer
cargo test database --lib -- --quiet
# Database plugins (SQLite)
cargo test --test database_plugins_comprehensive_test --features sqlite
# PostgreSQL (requires Docker)
./scripts/testing/test-postgres.sh
# Run benchmarks (if configured)
cargo bench --bench '*' || echo "No benchmarks configured"
# Parallel execution (default, faster)
cargo test --all-features
# Sequential execution (for database tests with shared state)
cargo test --all-features -- --test-threads=1
# Show only pass/fail summary
cargo test --all-features --quiet
# Show println! and debug output
cargo test --all-features -- --nocapture
# Run tests and show only failures
cargo test --all-features 2>&1 | grep -A 10 "FAILED"
# Run specific test
cargo test test_vdot_calculation
# Run tests matching pattern
cargo test multitenant
# Run tests in specific module
cargo test intelligence::algorithms
# Test with specific features
cargo test --features sqlite
cargo test --features postgresql
cargo test --features testing
# Skip expensive tests
cargo test --all-features -- --skip test_expensive_operation
# Skip integration tests
cargo test --lib
# Fast check (unit tests only)
cargo test --lib --quiet
# Full test suite
cargo test --all-features
# Specific test with output
cargo test test_name -- --nocapture
# Multi-tenant isolation
cargo test --test mcp_multitenant_complete_test
# Intelligence algorithms
cargo test --test intelligence_tools_basic_test
# Database tests
cargo test database
# Protocol compliance
cargo test protocol
# Authentication
cargo test auth oauth
# Full CI validation
./scripts/ci/lint-and-test.sh
scripts/ci/lint-and-test.sh - Full CI validation suitetests/ - Integration tests directorytests/common.rs - Shared test utilitiestest-multitenant-isolation - Multi-tenant testingtest-intelligence-algorithms - Algorithm validationtest-mcp-compliance - Protocol complianceUse when designing prompts for LLMs, optimizing model performance, building evaluation frameworks, or implementing advanced prompting techniques like chain-of-thought, few-shot learning, or structured outputs.
How to deploy Dravr infrastructure and apply Cloud Run config changes. Use when editing infra/ terraform, when a merged code change is live but a Cloud Run setting (cpu, memory, min/max instances, env var, scaling) hasn't taken effect, or when asked to plan/apply infra. Explains the two-pipeline model (app binary auto-deploys on push; terraform infra config is a separate manual apply) plus the cpu/cpu_idle guardrails.
Enforces zero-tolerance code quality policy using Clippy with strict lints, all warnings treated as errors
Write well-formatted notes to the dravr-vault Obsidian knowledge base. Use this skill whenever creating or updating an ADR, runbook, plan, API doc, guide, session output, or any structured document that should land in the vault — even when the user doesn't say "Obsidian" explicitly. Delegates to obsidian:obsidian-cli to write to the live vault and applies Dravr frontmatter and formatting standards.
Bootstrap Pierre server with database, admin user, coaches, and test users for development and testing
Validates coach markdown files for required frontmatter fields, sections, and naming conventions