Run recursive self-test on FlutterTester dashboard using bingo pipeline
From opentestersnpx claudepluginhub otmo123/opentesters/self-testRuns behavioral tests comparing baseline Claude responses against stay-on-target enhanced prompts across scenarios, grading with rubrics, and producing Markdown results file with summary.
/self-testSelf-improvement loop targeting test coverage. Iteratively generates and improves tests until a coverage target is met or iterations exhausted.
/self-testRun zero-cost in-session plugin validation. Enumerates all skills, agents, and commands from the plugin manifest, verifies file existence, validates frontmatter, checks trigger phrase quality, flags ambiguous overlaps, and generates synthetic test prompts. Use when validating plugin health, checking component coverage, auditing trigger descriptions, or verifying no components are missing or broken. Trigger with phrases like "self-test", "validate plugin", "check plugin health", "plugin coverage report", "test plugin components", "audit plugin triggers".
Run OpenTester's bingo pipeline against the FlutterTester dashboard itself — a recursive self-test that exercises the entire QA system.
/opentesters:self-test [--publish] [--repair]
Examples:
/opentesters:self-test — run self-test, show results/opentesters:self-test --publish — run and publish findings to GitHub/opentesters:self-test --repair — run with Opus repair agentThe FlutterTester dashboard (in flutter_tester/) is tested as a real Flutter app:
Call mcp__opentesters__bingo_board with:
FlutterTesterstaticflutterflutter_tester/Call mcp__opentesters__bingo_interview with audit settings:
{
"accessibility": true,
"performance": true,
"solid": true,
"stride": true
}
Call mcp__opentesters__bingo_verify with the board ID
Spawn gate agents:
flutter analyze, flutter test)Use post_agent_conversation to stream all agent activity to any connected dashboard
Call mcp__opentesters__synthesize_issue to compile findings
If --publish: create GitHub issue with findings
Self-testing typically discovers:
This is intentionally recursive — OpenTester tests its own dashboard, which displays the test results in real-time via the Conversation tab. The agents can see themselves running.