docs Testing and automation
History and diffing
Browse, replay and diff past responses.
- Every successful request produces a history entry with request text, method, status, duration, and a body snippet (unless
@no-logis set). Values injected from-secretcaptures and allowlisted sensitive headers (Authorization, Proxy-Authorization,X-API-Key,X-Access-Token,X-Auth-Key,X-Amz-Security-Token, etc.) are masked automatically unless you opt-in with@log-sensitive-headers. - History entries are environment-aware; selecting another environment filters the list automatically. Grouped entries store the display label together with the structured selection, and replaying one restores that selection when it still resolves. If a group or profile no longer exists, Resterm keeps the current selection, shows a warning, and refuses an immediate resend rather than silently running with different credentials.
- When focused on the history list, press
Enterto load a request into the editor without executing it. User/Ctrl+R(or your normal send shortcut such asCtrl+Enter/Cmd+Enter) to replay the loaded entry. - The Diff tab compares focused versus pinned panes, making regression analysis straightforward.
- 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 is automatically repopulated so you can audit deltas 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.