Best use case
test-ops is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. テスト計画・実行・報告を標準化する運用スキル。
テスト計画・実行・報告を標準化する運用スキル。
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "test-ops" skill to help with this workflow task. Context: テスト計画・実行・報告を標準化する運用スキル。
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/test-ops/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How test-ops Compares
| Feature / Agent | test-ops | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
テスト計画・実行・報告を標準化する運用スキル。
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## テスト実装戦略 ### テスト設計原則 - **網羅性**: 正常ケース、エラーケース、境界値、エッジケースを全て実装 - **独立性**: 各テストは他のテストに依存せず独立して実行可能 - **可読性**: テストコードは仕様書として機能するよう明確に記述 - **保守性**: テスト対象の変更に対して柔軟に対応できる構造 ### モック化戦略 - **DBアクセス**: リポジトリパターンでモック化またはフィクスチャを使用 - **外部API**: HTTPクライアントをモック化し、レスポンスパターンを網羅 - **時間依存処理**: 現在時刻やタイマー処理は固定値でモック化 - **ファイルI/O**: ファイルシステムアクセスは仮想ファイルシステムを使用 ### テスト実装手順 1. **機能分析**: テスト対象コンポーネントの全機能を詳細に調査 2. **テストケース設計**: 機能ごとに正常 / 異常 / 境界値ケースを洗い出し 3. **テスト実装**: テスト対象コードは変更せずテストのみ実装 4. **実行確認**: 全てのテストが期待通りに通過することを確認 5. **カバレッジ確認**: コードカバレッジ 100% を目指す ### テストコード品質基準 - **AAA パターン**: Arrange（準備）、Act（実行）、Assert（検証）を明確に分離 - **テスト名**: テスト内容が一目で分かる日本語での命名 - **アサーション**: 期待値と実際の値を明確に比較 - **エラーメッセージ**: 失敗時に問題箇所が特定できるメッセージ
Related Skills
testing-strategies
Design comprehensive testing strategies for software quality assurance. Use when planning test coverage, implementing test pyramids, or setting up testing infrastructure. Handles unit testing, integration testing, E2E testing, TDD, and testing best practices.
backend-testing
Write comprehensive backend tests including unit tests, integration tests, and API tests. Use when testing REST APIs, database operations, authentication flows, or business logic. Handles Jest, Pytest, Mocha, testing strategies, mocking, and test coverage.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
game-test-case-generator
基于需求文档（xls/csv）生成专业游戏测试用例，支持完整用例和快速测试点两种模式。当用户提到"游戏测试"、"测试用例生成"、"需求转测试用例"、上传需求文档或原型时使用此技能。
wordpress-penetration-testing
This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vulnerabilities", or "use WPScan". It provides comprehensive WordPress security assessment methodologies.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
web-security-testing
Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.
unit-testing-test-generate
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
testing-qa
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
test-fixing
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
test-automator
Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration. Use PROACTIVELY for testing automation or quality assurance.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.