(opencode-project - Skill) Implement comprehensive testing for Cloudflare Workers and SvelteKit applications using Vitest, Playwright, and Miniflare for unit, integration, and end-to-end testing in serverless environments.
Guidance for running and debugging tests in Docker environments for FastAPI + Vue/Tailwind projects.
Guidance for working on the Node+Express app with health checks, image uploads, and Playwright/Vibium tests.
Test Nuxt 3 / Nitro applications - both API handlers (real PostgreSQL, transaction rollback) and frontend components (@nuxt/test-utils, mountSuspended).
Comprehensive Playwright automation testing skill with E2E testing standards, test generation workflows, and browser automation best practices. Use when writing automated browser tests, testing user flows, or performing web application QA.
Flutter testing patterns for aviation EFB applications. Use when writing unit tests, widget tests, integration tests, or golden tests. Includes mocking strategies for location/sensors, test fixtures for aviation data, and patterns for testing BLoC state management, offline scenarios, and safety-critical navigation calculations.
Use when writing, running, or debugging Flutter tests. Provides testing patterns, commands, and best practices for the Rmotly app.
Test SwiftUI apps with XCTest, UI tests, snapshot testing, and async testing. Use when writing unit tests for ViewModels, creating UI automation tests, implementing snapshot tests, or testing async code.
Use when testing Android apps on ADB-connected devices/emulators - UI automation, screenshots, location spoofing, navigation, app management. Triggers on ADB, emulator, Android testing, location mock, UI test, screenshot walkthrough.
Testing and validation workflows for the Radar Tinder mobile application built with Expo + React Native, Firebase (Auth, Firestore, Realtime/Cloud Functions), Maps APIs, and on-device ONNX inference. This skill should be used for regression testing, feature verification, realtime issues, leaderboard inconsistencies, navigation bugs, and AI diagnostics validation.
Testing and QA for tvOS - XCUITest with remote simulation, screenshots, navigation tracking, TestFlight distribution. Triggers on testing, XCUITest, TestFlight, QA, automation, screenshots, beta testing.
Test iOS apps using AXe CLI for accessibility auditing, UI automation, and simulator control. Use when testing iOS Simulator apps, automating UI interactions, recording test videos, or auditing accessibility labels and VoiceOver support.
Flutter testing patterns with mocktail. Covers unit testing, widget testing, and BLoC/Cubit testing. Use when writing tests or setting up test infrastructure.
E2E testing and mobile automation for Flutter apps. Use when creating/running tests with Maestro, Mobile MCP, and Dart MCP.
Execution workflow preferences including no dev servers, read-only information gathering, real data over mocks, and proper error handling over fallbacks. Use when executing code, running servers, testing, or handling data.
Execute tests adaptively, analyze failures, generate detailed failure reports, and iterate until tests pass. This skill should be used when running tests from a test plan, working with any language, framework, or test type (E2E, API, unit, integration, performance).
Test features, debug issues, run manual or automated tests, collect logs. Use when testing, debugging, validating, running tests, or analyzing errors.
Comprehensive Playwright E2E testing framework for browser automation. Use when setting up tests, writing E2E scenarios, debugging test failures, configuring CI/CD pipelines, or running browser automation on WSL2.
Comprehensive guide for writing shell script tests using Bats (Bash Automated Testing System). Use when writing or improving tests for Bash/shell scripts, creating test fixtures, mocking commands, or setting up CI/CD for shell script testing. Includes patterns for assertions, setup/teardown, mocking, fixtures, and integration with GitHub Actions.
Elite testing skill for creating comprehensive, production-grade test suites with meaningful coverage. Use when (1) writing new test files or test suites, (2) improving test coverage for existing code, (3) the user requests "test", "testing", "write tests", "test coverage", or "unit tests", (4) creating integration, e2e, or API tests, (5) validating code quality through testing, (6) setting up testing infrastructure, or (7) the user explicitly wants tests that catch real bugs, not just superficial coverage.
This skill should be used when the user asks to "テストのドキュメントを作成", "create test document", "テストをレビュー", "review tests", "テスト網羅性を確認", "test coverage", "テストマトリクスを作成", "テストが十分か確認", "必要なテストを洗い出し", "テスト設計", "テストケース一覧", "missing tests", "テストの漏れがないか", "what tests are needed". (project)
