How do I install the Restassured Documentation Assertion Strength Report skill?

Run npx skillmds@latest add jovd83/restassured-documentation-assertion-strength-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Which AI agents work with Restassured Documentation Assertion Strength Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Who published Restassured Documentation Assertion Strength Report?

jovd83 (@jovd83) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Restassured Documentation Assertion Strength Report by jovd83

Name: Restassured Documentation Assertion Strength Report
Author: jovd83

Restassured Documentation Assertion Strength Report

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.

jovd83 Updated Sep 17, 2026

File contents

Build Assertion Strength Report

1. Gather Inputs

Require the Rest Assured test sources.
Require docs/testing/test-mapping-report.md when endpoint context is needed.

2. Choose The Files

Prefer docs/testing/assertion-strength-report.md.
When the user wants a human-friendly report, also generate docs/testing/html/assertion-strength-report.html.

3. Build The Assessment

Score each test method from the code, not from assumptions.
Detect status, header, content-type, body, schema, and workflow-style assertions.
Classify each test method as Weak, Moderate, or Strong.
Call out tests that only assert status codes or only transport-level behavior.
Recommend where semantic assertions should be added next.

4. Output Shape

Start from assertion-strength-report-template.md.
Keep the exact section headings stable.
Run python scripts/generate_assertion_strength_report.py --tests-root <tests-root> --mapping <mapping-md> --output-md <report-md> --output-html <report-html>.

5. Keep It Actionable

Highlight the weakest tests first.
Explain why a test is weak or strong.
Update the session-state artifact after generating or changing the report.

6. Examples

Input: Which tests only assert status codes? Output: Create an assertion-strength report that classifies tests and isolates weak ones.
Input: Assess the quality of these Rest Assured assertions. Output: Produce a markdown and HTML report with strengths, weaknesses, and recommended next assertions.

7. Troubleshooting

Problem: The same test method mixes several requests. Fix: Score the whole method and label it as workflow-oriented when multiple HTTP calls are present.
Problem: The repo uses helper methods for assertions. Fix: Mark the result as approximate and recommend manual review for the affected tests.

---name: restassured-documentation-assertion-strength-reportdescription: 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.---# Build Assertion Strength Report## 1. Gather Inputs1. Require the Rest Assured test sources.2. Require `docs/testing/test-mapping-report.md` when endpoint context is needed.## 2. Choose The Files1. Prefer `docs/testing/assertion-strength-report.md`.2. When the user wants a human-friendly report, also generate `docs/testing/html/assertion-strength-report.html`.## 3. Build The Assessment1. Score each test method from the code, not from assumptions.2. Detect status, header, content-type, body, schema, and workflow-style assertions.3. Classify each test method as `Weak`, `Moderate`, or `Strong`.4. Call out tests that only assert status codes or only transport-level behavior.5. Recommend where semantic assertions should be added next.## 4. Output Shape1. Start from [assertion-strength-report-template.md](assets/assertion-strength-report-template.md).2. Keep the exact section headings stable.3. Run `python scripts/generate_assertion_strength_report.py --tests-root <tests-root> --mapping <mapping-md> --output-md <report-md> --output-html <report-html>`.## 5. Keep It Actionable1. Highlight the weakest tests first.2. Explain why a test is weak or strong.3. Update the session-state artifact after generating or changing the report.## 6. Examples1. Input: `Which tests only assert status codes?` Output: Create an assertion-strength report that classifies tests and isolates weak ones.2. Input: `Assess the quality of these Rest Assured assertions.` Output: Produce a markdown and HTML report with strengths, weaknesses, and recommended next assertions.## 7. Troubleshooting1. Problem: The same test method mixes several requests. Fix: Score the whole method and label it as workflow-oriented when multiple HTTP calls are present.2. Problem: The repo uses helper methods for assertions. Fix: Mark the result as approximate and recommend manual review for the affected tests.

Frequently asked questions