Add documentation on testing hooks

gjtorikian · gjtorikian · commit 7c67ed193c9a · 2014-01-27T16:01:14.000-08:00
diff --git a/content/hooks/configuring/index.md b/content/hooks/configuring/index.md
@@ -56,7 +56,6 @@ setup might look something like this:
       puts "I got some JSON: #{push.inspect}"
     end
 
-
 (If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra guide].)
 
 Start this server up.
@@ -79,7 +78,7 @@ were setting up a "real" web application, you might want to log some of the JSON
 output to a database.
 
 For additional information on working with webhooks for fun and profit, head on
-over to the [Testing Webhooks][/hooks/testing] guide.
+over to the [Testing Webhooks](/hooks/testing) guide.
 
 [platform samples]: https://github.com/github/platform-samples/tree/master/hooks/ruby/configuring-your-server
 [Sinatra]: http://www.sinatrarb.com/
diff --git a/content/hooks/testing/index.md b/content/hooks/testing/index.md
@@ -5,36 +5,36 @@ layout: hooks
 
 # Testing Hooks
 
-(TODO: are we going to continue to recommend outside services, like RequestBin?)
-
-### Configuring the Server
-
-Now, the fun part. We'll set up a basic Sinatra server to handle incoming payloads:
-
-```ruby
-require 'sinatra'
-require 'rest_client'
-require 'json'
-
-post '/callback' do
-  puts request.body.read
-end
-```
-
-
-```json
-{
-   "payload":{
-      "ref":"refs/heads/master",
-      "after":"9a21d582f13c5b652c2c9546322bbf71682d3f06",
-      "before":"05333fedb2f49ee2dd0dcc24b01d3d964f43c255",
-   },
-   ...
-   "event":"push",
-   "config":{
-      "greeting_message":"Hey, how it's going~!",
-      "url":"http://4pw3.localtunnel.com/callback"
-   },
-   "guid":"6168aab4-4737-11e3-9ac9-7403c7a52ec3"
-}
-```
+* TOC
+{:toc}
+
+Now that you've [configured your local server](/hooks/configuring/), you might
+be interested in pushing your code to the limits. To that end, GitHub's webhooks 
+view provides some tooling for testing your deployed payloads.
+
+
+## Listing recent deliveries
+
+Every webhook has its own "Recent Deliveries" section, which lists, at a glance
+whether a deployment was successful (green dot) or failed (red dot).
+
+![Recent Deliveries view](/images/webhooks_recent_deliveries.png)
+
+You can also identify when each delivery was attempted.
+
+## Digging into results
+
+By expanding an individual delivery, you'll be able to witness *precisely*
+what information GitHub is attempting to send to your server. This includes
+both the HTTP Request and Response.
+
+### Request
+
+The webhook delivery view provides information on which Headers were sent by GitHub.
+It also includes details about the JSON payload.
+
+## Response
+
+The response tab lists how your server replied once it received the payload from 
+GitHub. This includes the status code, the headers, and any additional data
+within the response body.
diff --git a/static/images/webhooks_recent_deliveries.png b/static/images/webhooks_recent_deliveries.png
