Skip to content
HTTP / RICH / ROBOT FRAMEWORKFROM EXCHANGE TO DIAGNOSIS

Every exchange.In plain sight.

Requests, responses and assertions in your Robot console.

Get startedExplore the console
FICTIONAL CASE / BOOKSConsult book
01

Request

GET/books/42

api_key=[REDACTED]

Sensitive data protected in the output.

02

Response

HTTP200.

{ "title": "" }

The service responded. The title is empty.

03

Recorded assertion

Title has a valueFAIL.

Book title must contain a value

The test records the failed assertion.

CONSOLE OUTPUTSummary · Consult book
GET http://127.0.0.1:36519/books/42?tag=one&tag=two&api_key=%5BREDACTED%5D
HTTP 200 · 1.16 ms
Book title must contain a valueFAIL'' should not be empty.
Actual excerpt · The complete output is below.WHEN THE TEST CLOSES

A fictional book test case with an intentional failure. Actual output from the same test is below.

Discover Request LoggerAN HTTP STATUS DOES NOT TELL THE WHOLE STORY.

Choose how much to see

  • Summary

    A compact view of every exchange.

  • Failures

    Focus on the operations associated with recorded failures.

  • Full

    Read protected headers and bodies with JSON highlighting.

poetry add robotframework-request-logger

Start simple

mode=summary is the default. Keep Robot's usual console; you do not need to change your execution command.

The console, as generated

These images are Rich SVG exports from the project’s executable tests. The fictional book example returns HTTP 200 with an empty title; the test records a failing title assertion. Each tab shows the actual output.

Request Logger · Summary

Request Logger · Failures

Request Logger · Full

See how to reproduce these outputs · Download the test case

Output is printed when the test ends. Buffering allows failure filtering and applies known secrets across the entire test before any block is printed.

Follow the exchange

flowchart TD
    A[RequestsLibrary] --> B[Log Response]
    B --> C[Log Assertion Result]
    C --> D[Console]

Explore JSON themes