zero-script-qa

Zero Script QA——无需测试脚本的测试方法。采用结构化 JSON 日志记录与实时 Docker 监控。当用户需要通过日志分析来验证功能时，请主动使用此技能。触发条件：zero script qa、基于日志的测试、Docker 日志、 제로 스크립트 QA、테스트、로그 분석、ゼロスクリプトQA、ログ分析、零脚本QA、日志分析、 QA sin scripts、logs-based testing、 QA sans script、tests basés sur les logs、 skriptloses QA、log-basiertes Testen、 QA senza script、test basati sui log、请勿用于：单元测试或未使用 Docker 的项目

SKILL.md

--- frontmatter

name: zero-script-qa
description: |
  Zero Script QA - Testing methodology without test scripts.
  Uses structured JSON logging and real-time Docker monitoring.

  Use proactively when user needs to verify features through log analysis.

  Triggers: zero script qa, log-based testing, docker logs,
  제로 스크립트 QA, 테스트, 로그 분석,
  ゼロスクリプトQA, ログ分析,
  零脚本QA, 日志分析,
  QA sin scripts, pruebas basadas en logs,
  QA sans script, tests basés sur les logs,
  skriptloses QA, log-basiertes Testen,
  QA senza script, test basati sui log

  Do NOT use for: unit testing, projects without Docker

Zero Script QA

Testing methodology using structured logging instead of test scripts

Philosophy

Instead of writing and maintaining test scripts, Zero Script QA uses:

•Structured JSON logging for all operations
•Real-time Docker log monitoring
•Pattern-based verification

Key Principles

1. Structured Logging

typescript

// Every operation logs structured JSON
logger.info({
  event: 'user.login',
  userId: user.id,
  method: 'email',
  success: true,
  duration: 234
});

2. Log Patterns

Define expected patterns for verification:

json

{
  "feature": "user-login",
  "patterns": [
    {"event": "user.login", "success": true},
    {"event": "session.created"},
    {"event": "audit.login"}
  ]
}

3. Real-time Monitoring

bash

# Monitor Docker logs in real-time
docker logs -f app-container 2>&1 | grep -E '"event":'

Usage

bash

# Start QA monitoring
/zero-script-qa start

# Monitor specific feature
/zero-script-qa monitor user-login

# Generate QA report
/zero-script-qa report

Benefits

Traditional Testing	Zero Script QA
Write test scripts	Define log patterns
Maintain test code	Logs are automatic
Flaky tests	Consistent logs
Separate test env	Same as production

Log Categories

•Business Events: User actions, transactions
•System Events: Startup, shutdown, errors
•Performance Metrics: Response times, throughput
•Security Events: Auth, access control

Integration

Works with:

•Docker Compose
•Kubernetes
•Any JSON logging system