Record
Record HTTP traffic flows into reusable script files for later replay or regression testing.
The record subcommand captures traffic into a portable script file that you can replay later. This enables a record-once, replay-many workflow for regression testing: record production or staging traffic once, then replay it against new builds to verify behavior hasn't changed.
record start
Start recording traffic. All sessions captured after this point are stored in the recording buffer.
httpeep-cli record startrecord stop
Stop recording and save the captured traffic to a file.
httpeep-cli record stop --output test-flow.httpeep| Flag | Description |
|---|---|
--output <path> / -o <path> | Output file path for the recording |
record status
Check whether a recording is currently in progress.
httpeep-cli record statusTypical workflow
# Start recording
httpeep-cli record start
# Run your tests or interact with your application
npm run integration-tests
# Stop and save
httpeep-cli record stop --output baseline.httpeepThe output file is a self-contained script that stores the full request sequence, including headers, bodies, and timing metadata. You can replay it later with:
httpeep-cli replay file baseline.httpeepCombine recording with focused host filtering in your test suite to keep script files small and fast to replay.
Replay
Replay captured HTTP sessions from the command line. Replay by session ID with retry, replay from a script file, or replay the most recently captured request.
Certificate
Manage the HTTPS interception root CA certificate: install to the system trust store, check status, or export for manual installation.