Webhook Tester

Devtools toolkit for tracking and managing webhook testing operations. Log checks, validations, linting results, diffs, and reports — all with timestamped history and multi-format export.

Commands

All data commands accept optional input. Without input, they display the 20 most recent entries. With input, they log a new timestamped entry.

Core Operations

Utility Commands

Data Storage

All data is stored locally in ~/.local/share/webhook-tester/:

• Per-command logs: check.log, validate.log, lint.log, diff.log, etc. — one file per command type
• History log: history.log — unified activity log with timestamps
• Export files: export.json, export.csv, export.txt — generated on demand
• Format: Each entry is stored as YYYY-MM-DD HH:MM|<input> (pipe-delimited)

Set the WEBHOOK_TESTER_DIR environment variable to override the default data directory.

Requirements

• bash (with set -euo pipefail strict mode)
• Standard Unix tools: date, wc, du, head, tail, grep, basename, cat
• No external dependencies or API keys required

When to Use

1. Tracking webhook validation results — Log validation outcomes for payloads from Stripe, GitHub, Slack, etc. and review patterns over time
2. Recording lint and format checks — Use lint and format to track payload quality checks during integration development
3. Documenting webhook fixes and debugging — Use fix, explain, and diff to maintain a structured record of debugging sessions
4. Comparing webhook payloads across versions — Use diff and compare to log differences between expected and actual payloads during schema migrations
5. Exporting test records for compliance — Pull all logged data into JSON, CSV, or TXT for QA sign-off, audit trails, or integration documentation

Examples

# Log a webhook validation result
webhook-tester validate "Stripe checkout.session.completed — signature verified OK"

# Record a linting result
webhook-tester lint "GitHub push event payload: missing 'ref' field in 3 of 12 test cases"

# Log a diff between expected and actual payloads
webhook-tester diff "v2 vs v3 payload: added 'metadata.source' field, removed 'legacy_id'"

# Document a fix applied to a webhook handler
webhook-tester fix "added retry logic for 429 responses from payment gateway"

# View recent check entries
webhook-tester check

# Search for entries related to a specific integration
webhook-tester search "Stripe"

# Get summary statistics across all categories
webhook-tester stats

# Export everything to JSON for analysis
webhook-tester export json

# Check tool health and data directory status
webhook-tester status

# View the 20 most recent activity entries
webhook-tester recent

How It Works

Webhook Tester uses a simple append-only log architecture. Each command type writes to its own .log file, and all activity is also appended to a central history.log for chronological tracking. The stats command aggregates counts across all log files. The export command reads all logs and serializes them into the requested format (JSON array, CSV with headers, or plain text sections). The search command performs case-insensitive grep across all log files.

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com