docs Testing and automation
History and diffing
Browse, replay and diff past responses.
-
Every successful request saves its request text, method, status, duration, and a body snippet to history.
@no-logomits the body snippet. Secret values show as•••. Sensitive headers on Resterm's list (such as Authorization, Proxy-Authorization,X-API-Key,X-Access-Token,X-Auth-Key, andX-Amz-Security-Token) are masked too unless you opt in with@log-sensitive-headers. If a later request reveals a new secret, for example through a-secretcapture, Resterm masks it in the entries saved earlier in the same session. When those responses add up to more than 16 MiB, it masks the oldest body snippets whole instead, along with any single one over 16 MiB. -
History entries remember their environment, and switching environments filters the list. Grouped entries save both the display label and the individual group selections. Replaying an entry restores those selections if they still exist.
If a group or profile has been removed, Resterm keeps the current selection, shows a warning, and blocks the immediate resend. This prevents a replay from silently using different credentials.
-
With the history list focused, press
Enterto load a request into the editor without sending it. User/Ctrl+R(or your normal send shortcut such asCtrl+Enter/Cmd+Enter) to replay the loaded entry. -
The Diff tab compares the focused pane with the pinned one, which helps you spot regressions.
-
Compare runs are stored as grouped rows (
COMPAREmethod), including the varied group, target profile, and full selection for each row. The preview (p) shows the entire bundle,Enterloads the failing (or baseline) environment back into the editor, and the Compare tab fills in again so you can review the differences offline.
JSON reports stay at schema version 1. Grouped runs add environmentSelection and compare.group, while the existing envName and environment strings keep the full display label. Text and JUnit output only use those labels.