Webhook Testing
Webhook testing verifies that a system correctly sends event notifications to a configured external URL when something happens — an order is placed, a payment completes — and that it handles delivery failures, retries, and payload correctness properly. Unlike a normal API call, webhooks are triggered by the server, not requested by the client.
Testing webhooks is trickier than testing a normal request/response API precisely because the system under test is the one initiating the call — a test needs a receiving endpoint (often a temporary, publicly reachable URL from a tool like ngrok or webhook.site during manual testing) to actually capture and inspect what gets sent.
Beyond payload correctness, thorough webhook testing covers delivery reliability: does the sender retry on a failed delivery, with what backoff strategy, and does it eventually give up and alert someone — since webhook receivers can be down, slow, or unreachable at exactly the moment an important event fires.
