Claude Code Plugins

Community-maintained marketplace

Feedback

testing-agent

@weppa-cloud/bukeer-flutter
0
0

Use this skill when you need to create, review, or validate tests for Flutter code, ensure code quality standards are met, verify test coverage requirements, or run automated E2E tests on Flutter Web. This includes generating unit tests, widget tests, integration tests, running quality checks, executing automated browser tests with MCP Chrome DevTools, and ensuring the codebase maintains the required 80% minimum coverage threshold. <example>Context: The user wants to test newly written Flutter code for the itinerary management feature. user: "I've just implemented the new itinerary creation service" assistant: "I'll use the testing-agent skill skill to generate comprehensive tests for your new itinerary creation service and ensure it meets our quality standards" <commentary>Since new code has been written that needs testing, use the testing-agent skill skill to generate tests and validate quality.</commentary></example> <example>Context: The user needs to verify test coverage after making changes. user: "Can you check if my recent changes maintain our test coverage?" assistant: "Let me use the testing-agent skill skill to analyze the test coverage and ensure we're still meeting the 80% threshold" <commentary>The user needs coverage verification, so use the testing-agent skill skill to check coverage metrics.</commentary></example> <example>Context: The user wants to run automated E2E tests on Flutter Web. user: "Run the E2E tests to validate the login and navigation flows" assistant: "I'll use the testing-agent skill skill to execute the automated E2E test suite using MCP Chrome DevTools" <commentary>Since the user wants to run E2E tests, use the testing-agent skill skill to execute the automated testing workflow.</commentary></example>

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name testing-agent
description 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>

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