README.md in capybara-json-0.3.0 vs README.md in capybara-json-0.4.0
- old
+ new
@@ -1,8 +1,8 @@
# capybara-json [![Build Status](https://secure.travis-ci.org/okitan/capybara-json.png?branch=master)](http://travis-ci.org/okitan/capybara-json) [![Dependency Status](https://gemnasium.com/okitan/capybara-json.png)](https://gemnasium.com/okitan/capybara-json)
-testing ruby: 1.9.2, 1.9.3; Capybara: 0.4.x, 1.1.x, 2.0.x
+testing ruby: 1.9.2, 1.9.3, 2.0.0; Capybara: 0.4.x, 1.1.x, 2.0.x
## About capybara-json
capybara-json provides the same interface to testing JSON API (both local and remote)
@@ -15,24 +15,28 @@
include Capybara::Json
Capybara.current_driver = :rack_test_json
Capybara.app = MyRackApp
post '/', { "this is" => "json" } # POST '/'
-json #=> parsed json response
-source #=> raw response body
+json #=> parsed json response
+raw_json #=> raw response body
+
get '/errors/400'
status_code #=> 400
get! '/errors' #=> raise Capybara::Json::Error
-get '/errors', {}, { 'header' => '' } # request headers
-response_headers #=> response headers
+get '/errors', {}, { 'header' => '' } # set request headers
+response_headers #=> get response headers
+
Capybara.current_driver = :httpclient_json
Capybara.app_host = 'http://example.com'
post '/', { "this is" => "json" } # POST 'http://example.com/'
-json #=> parsed json response
-source #=> raw response body
+json #=> parsed json response
+raw_json #=> raw response body
+
get '/errors/400'
status_code #=> 400
get! '/errors' #=> raise Capybara::Json::Error
-get '/errors', {}, { 'header' => '' } # request headers
-response_headers #=> response headers
+
+get '/errors', {}, { 'header' => '' } # set request headers
+response_headers #=> get response headers
```