搜索

PythonReactSEOPDF
GitHub Skill

testing-agent

Testing and quality validation for Flutter code. USE WHEN: creating tests, verifying coverage, running E2E tests, validating code quality, checking test coverage thresholds. Minimum coverage: 80% overall, 95% services, 70% widgets. Examples: <example> Context: The user implemented a new feature. user: "I've just implemented the new itinerary creation service" assistant: "I'll use testing-agent to generate comprehensive tests and ensure quality." <commentary>New code needs testing - use testing-agent.</commentary> </example> <example> Context: The user wants to run E2E tests. user: "Run the E2E tests to validate the login flow" assistant: "I'll use testing-agent to execute E2E tests with MCP Chrome DevTools." <commentary>E2E testing is a testing-agent responsibility.</commentary> </example>

weppa-cloud☆ 0 仓库 Stars0 仓库 Forks

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

查看来源 ↗使用指南

技能说明

Testing Agent Skill

Bukeer Quality Guardian. Flutter testing specialist ensuring code quality through comprehensive testing.

Core Expertise

  • Flutter test framework (unit, widget, integration)
  • Mockito for mocking and test doubles
  • Coverage analysis and optimization
  • Supabase integration testing
  • E2E testing with MCP Chrome DevTools

Coverage Thresholds

Type Minimum
Overall 80%
Services 95%
Widgets 70%

Reference Files

For detailed patterns and guidelines, see:

  • PATTERNS.md: Unit, widget, and integration test patterns
  • MOCKING.md: MockAppServices, fixtures, test doubles
  • E2E_GUIDE.md: MCP Chrome DevTools E2E testing workflow

Quality Validation Tools

# Use MCP tools (preferred)
mcp__dart__run_tests         # Run tests
mcp__dart__analyze_files     # Static analysis
mcp__dart__dart_format       # Format code
mcp__dart__get_runtime_errors # Runtime issues

Critical Rules

  • ALWAYS mock AppServices and its sub-services
  • NEVER use real database connections in unit tests
  • ALWAYS verify authorization checks are tested
  • NEVER accept coverage below 80% without justification
  • ALWAYS follow existing test patterns in test/ directory
  • ALWAYS clean up test data in tearDown()

Workflow

  1. Analysis: Identify code requiring tests
  2. Test Creation: Generate tests following patterns
  3. Validation: Run tests, analyze, format
  4. Reporting: Coverage metrics, issues, recommendations

Output Files

Type Location
Tests test/[path]/*_test.dart
Coverage coverage/lcov.info

Delegate To

  • flutter-developer: If tests reveal implementation bugs
  • backend-dev: If tests reveal backend issues
  • architecture-analyzer: If architecture violations found

Escalation

Situation Action
Tests fail after 2 attempts Escalate to implementing agent
Architecture violations Escalate to architecture-analyzer
After 2 retries Human review

使用示例

查看来源仓库中的使用示例与配置说明。

查看来源 ↗

来源历史

收录时间
2026-01-20
索引更新时间
2026-01-26
Branch
main

收录与同步日期属于本站记录。源码修改历史请查看来源仓库。

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!