菜单
Use when Codex needs to assess whether Rest Assured tests are weak, moderate, or strong based on the assertions they make, the amount of API behavior they verify, and whether they go beyond status-code checks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | restassured-documentation-assertion-strength-report |
| description | Use when Codex needs to assess whether Rest Assured tests are weak, moderate, or strong based on the assertions they make, the amount of API behavior they verify, and whether they go beyond status-code checks. |
| metadata | {"author":"jovd83","version":"1.0","dispatcher-category":"testing","dispatcher-capabilities":"assertion-review, api-assertion-strength-review","dispatcher-accepted-intents":"assess_api_assertion_strength","dispatcher-input-artifacts":"api_test_suite, repo_context","dispatcher-output-artifacts":"assertion_strength_report, review_findings","dispatcher-stack-tags":"restassured, documentation, review","dispatcher-risk":"low","dispatcher-writes-files":false} |
docs/testing/test-mapping-report.md when endpoint context is needed.docs/testing/assertion-strength-report.md.docs/testing/html/assertion-strength-report.html.Weak, Moderate, or Strong.python scripts/generate_assertion_strength_report.py --tests-root <tests-root> --mapping <mapping-md> --output-md <report-md> --output-html <report-html>.Which tests only assert status codes?
Output: Create an assertion-strength report that classifies tests and isolates weak ones.Assess the quality of these Rest Assured assertions.
Output: Produce a markdown and HTML report with strengths, weaknesses, and recommended next assertions.Use when Codex needs to design, implement, run, document, or report Rest Assured API tests for REST services, contract-driven service tests, JUnit 5 automation, CI pipelines, or test-management integrations.
Use when Codex needs to derive Rest Assured test scenarios from OpenAPI or Swagger contracts, including endpoints, methods, schemas, auth rules, status codes, and error conditions.
Use when Codex needs to derive service-test scenarios from WSDL or SOAP contracts and translate them into HTTP and XML checks that can still be implemented with Rest Assured where appropriate.
Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.
Use when Codex needs to scaffold, retrofit, or normalize a Java Rest Assured test module with JUnit 5, Maven or Gradle, shared specifications, and an initial runnable smoke test.
Use when Codex needs to configure or troubleshoot Rest Assured API tests in CI pipelines, including JUnit 5 execution, tags, Docker, containers, artifacts, quality gates, and provider-specific pipeline examples.