测试与质量
3,371 个结果
- Capawesome Cloudcapawesome-teamGuides the agent through setting up and using Capawesome Cloud for Capacitor and Cordova apps. Covers three core workflows: (1) Native Builds — cloud builds for iOS and Android (Capacitor, Cordova, or native projects), signing certificates, environments, Trapeze configuration, and build artifacts; (2) Live Updates — OTA updates via the @capawesome/capacitor-live-update (Android, iOS, and…
- Ionic Angularcapawesome-teamGuides the agent through Angular-specific patterns for Ionic app development. Covers project structure, standalone vs NgModule architecture detection, Angular Router integration with Ionic navigation (tabs, side menu, modals), lazy loading, Ionic page lifecycle hooks, reactive forms with Ionic input components, Angular services for state management, route guards, performance optimization, and…
- Pipefy IpaaspipefyUse when the user wants to build, test, publish, or manage iPaaS (Advanced Automations) flows: multi-step integrations with external apps (Slack, Gmail, Google Sheets), incoming webhooks, schedules, routers, code steps, or iPaaS data tables. Driven through a per-pipe catalog discovered at runtime. For native if/then rules or prompt-driven AI automations, use `pipefy-automations` instead.
- Pipefy Pipes And CardspipefyUse this skill when the user wants to read, create, update, or delete pipes, phases, phase fields, labels, cards, comments, or field conditions. Use the seed-pipe-across-phases workflow when populating empty phases for demos or QA.
- API 接口测试fishzjpAPI testing from OpenAPI/Swagger or case schemas: parameters, boundaries, auth, idempotency, concurrency, error responses, data consistency; runnable scripts; k6 handoff. Not for: Web UI flows, manual case writing. 接口级测试：参数/边界/鉴权/幂等/并发/错误响应/数据一致性，产出脚本与结果；含 k6 压测。不用于：Web UI、手动用例。
- E2E 自动化测试fishzjpTurn manual cases into Playwright E2E automation run in a browser: page objects, helpers, bug evidence, reports. Not for: API tests, exploratory sessions, bug root-cause. 将手动用例转为 Playwright E2E 自动化并真实执行；含写自动化前的业务熟悉踩点、Page Object/Helper、Bug 证据与报告条目。不用于：API 接口测试、独立探索会话（exploratory-testing）、Bug 根因。
- 缺陷分析fishzjp对已确认的 Bug 做根因定位、影响分析、回归建议时使用——复现 → 读代码定位根因 → 影响五面分析 → 回归建议，条目（根因/影响/Severity 依据/修复建议/回归建议五个扩展字段）落盘为 Bug 条目。不用于：仅收集 Bug 证据（automated-e2e-testing / api-testing）、疑似未定性缺陷（test-case-writing 的 Cx 记录）。
- QA 共享知识库fishzjpqa-skills shared knowledge base — dependency, NOT triggerable: executability standards, evidence grading, risk model, type matrix, templates, scripts. Never invoke standalone; always install with the skills, or references break. 共享知识库（依赖单元，非触发 skill）：承载全系列引用的方法/模板/脚本。任何测试任务不要独立触发；装其他 skill 必须连装。
- 探索式测试fishzjpExploratory testing sessions when requirements are vague or docs are missing — charter-driven; outputs system understanding, risks, test ideas. Not for: automation prep, executing existing cases. 需求不完整、文档不足或系统陌生时发起独立探索式测试会话——charter 驱动，产出系统理解/风险清单/测试想法。不用于：为写自动化踩点（automated-e2e-testing 前置）、按既有用例执行。
- fishzjp/qa-skillsfishzjp技能合集Testing skills for AI coding agents: evidence-backed strategy, executable cases, Playwright/API testing, regression and QA memory. 面向 AI Agent 的测试工程技能。
- QA 测试流水线fishzjpEnd-to-end QA entry: "test this feature fully" orchestrates requirements, strategy, cases, review, execution, bugs, regression, report; resumable. Single-stage tasks use their stage skill. 端到端测试唯一入口：“帮我测试这个需求/功能”时编排需求→策略→用例→审查→执行→Bug 分析→回归→报告，落盘可续跑；单阶段诉求直接用对应阶段 skill。
- QA 项目知识库fishzjpMaintain the .qa/ knowledge base of cross-session QA knowledge (quirks, flaky verdicts, defect patterns, contract changes); read before test tasks. Not for: pipeline state, case files (test-case-writing). 维护被测项目 .qa/ 跨会话知识库（环境怪癖、flaky、缺陷模式、契约变更）读写治理；任务前先读取。不用于：流水线状态、用例文件读写（test-case-writing）。
- 回归测试fishzjpAfter a code change (diff/fix/requirement change), decide what to regression-test: changed files → functions → features → cases traceability; outputs a ranked list. Not for: editing case files (test-case-writing), long-term strategy (test-strategy). 代码变更后判断回归哪些测试：沿改动分析链产出分级回归清单。不用于：用例增量修改、长期策略。
- 测试用例评审fishzjpReview existing test cases (legacy, others', AI) for coverage and executability: build a testable-points baseline, assess independently, revise in place with records. Not for: writing cases from scratch (test-case-writing), pipeline. 审查已有用例（存量/他人/AI 产出）的覆盖与可执行性：先建基准再独立评估，修订留审查记录。不用于：从零写用例、写时自审、流水线。
- 测试用例设计fishzjpWrite manual test cases (markmap) from docs, bugs or code — code-first: review code for bugs first; extracts machine-readable schema. Not for: requirement-analysis / test-strategy / test-case-review / automation. 从 PRD/API 文档、Bug 或代码写手动用例（markmap）——代码优先：先查代码找 bug 再写，抽 Schema。不用于：需求建模、策略、评审、自动化。
- 测试可靠性治理fishzjpGovern flaky tests and suite reliability: rerun-pass verdicts, root-cause classes, quarantine, retry semantics, health metrics. Not for: in-run failures (e2e/api), triage, confirmed bugs. 治理 flaky 测试与套件可靠性：时好时坏/重跑变绿判定、根因四分类、隔离门禁、重试诚实语义、健康度。不用于：执行中单条失败（e2e/api）、批量分流（triage）、已确认 Bug（bug-analysis）。
- 测试策略fishzjp"How should this be tested?" Evidence-backed risk map → scope and depth across functional domains and 10 testing-type axes; includes carry signals, excludes reasons. Not for: writing cases, requirement-analysis, pipeline (qa). 回答“这个功能应该怎么测”：风险挂证据（Risk Map），译为功能域+类型域十轴的范围与深度。不用于：写用例、需求建模、流水线。
- Wuying Browser Useagentbay.ai自动化浏览器交互，用于网页测试、表单填写、截图和数据提取。当用户需要浏览网站、与网页交互或提取信息时使用。
- Backend TestingakillnessTurn backend test ambiguity into one practical backend test packet. Use when the user needs API/service/repository/auth-flow coverage design, fixture or seed/reset strategy, container-vs-mock dependency choices, contract/API compatibility checks, or flaky backend-suite stabilization across local and CI.
- Code RefactoringakillnessTurn a cleanup packet into one behavior-preserving refactor brief. Use when simplifying a messy function/component/service, freezing behavior before touching fragile legacy code, splitting a cleanup-heavy diff into reviewable slices, or planning a repeated migration / codemod without changing intended behavior.
- Game Design TheoryakillnessTurn a game-design question into one falsifiable theory packet instead of a framework collage. Use when a designer must explain why a mechanic may create a player experience, analyze mechanics-dynamics-aesthetics, test a core loop, inspect choice, uncertainty, progression, resource flow, mastery, autonomy, competence, or relatedness, compare design variants, or turn conflicting playtest…
- Motion LexiconRyan YangDesign, build, compose, implement, review, and contribute polished product interfaces with Motion Lexicon components and motion primitives. Use this skill when a user asks for a complete React page, landing page, dashboard, settings screen, or product surface in the Motion Lexicon visual language; asks what motion fits a UI event; needs a single interaction or multi-step product moment; requests…
- Research Paper WritingakillnessDraft and revise ML, CV, NLP, and systems research papers with strong claim-evidence flow, reviewer-aware structure, and submission-ready section planning. Use when the user needs help with an abstract, introduction, related work, method, experiments, ablations, discussion, figures/tables, checklist coverage, or rebuttal / response-letter writing for a paper.
- RtkakillnessInstall, initialize, verify, and troubleshoot RTK (Rust Token Killer) for AI coding agents. Use when you need to reduce shell-command token output, confirm that the correct `rtk` binary is installed, choose between Homebrew, install.sh, or Cargo installation, wire `rtk init` for Claude Code, Codex, Gemini CLI, Cursor, Copilot, Windsurf, Cline, or OpenCode, or use compact wrappers such as `rtk…