Status is one part. Content completes the story.

An HTTP 200 response can contain a value that fails an assertion. Request Reporter brings the request, response and assertions together so you can read the result in context. The cover interprets the empty title in a fictional book case. The HTML below is the actual file generated by the tool.

Capture. Validate. Share.

• 01 · Capture Response

  Keep the HTTP exchange alongside its test case.

• 02 · Assert

  Associate each validation with the corresponding request.

• 03 · HTML

  Share a standalone report, ready to open offline.

The report, exactly as generated

Three requests, four passing assertions and one intentional failure. Open Failures and select Book title must contain a value to reach Consult book and its exact failed assertion. You can also open the complete report.

Download the test case

Standalone HTML. Ready to open offline.

Requirements

Tool	Compatibility
Python	3.12+
Robot Framework	7.5+, within 7.x
RequestsLibrary	Executes HTTP; installed separately
DataDriver	Optional; generates cases from tabular data

How it works

flowchart TD
    A[RequestsLibrary: execute request] --> B[Capture Response: store response]
    B --> C[Assert: record assertions]
    C --> D[Listener: finish case]
    D --> E[Standalone HTML for Jira]

Only explicitly captured exchanges are included. Importing the library registers its listener; no CLI listener argument or generation keyword is required.

Metadata is optional

Add environment, identifiers or row data for context. The report works without them or an additional title.

Choose your route

• First use: install and run a case.
• Tabular data: generate DataDriver cases.
• Review results: read Summary, Failures and Assertions.
• Check arguments: Libdoc reference.
• Run the complete project: executable example, using Poetry and a fictitious local API.

You can also open a passing report without metadata. Each example contains one case; there is no suite-wide dashboard.