save_response

An 'httr' <code>response</code> object

response

logical: if <code>TRUE</code> (default), JSON responses with status 200
will be written as just the text of the response body. In all other cases,
and when <code>simplify</code> is <code>FALSE</code>, the "response" object will be written out to
a .R file using <code><a rd-options="base:dput" href="/link/base%3A%3Adput()?package=httptest&version=3.0.0&to=base%3Adput" data-mini-rdoc="base:dput::base::dput()">base::dput()</a></code>.

simplify

internal

Testing and documenting code that communicates with remote servers
can be painful. Dealing with authentication, server state,
and other complications can make testing seem too costly to
bother with. But it doesn't need to be that hard. This package enables one
to test all of the logic on the R sides of the API in your package without
requiring access to the remote service. Importantly, it provides three
contexts that mock the network connection in different ways, as well as
testing functions to assert that HTTP requests were---or were
not---made. It also allows one to safely record real API responses to use as
test fixture. The ability to save responses and load them offline also
enables one to write vignettes and other dynamic documents that can be
distributed without access to a live server.

Neal Richardson

httptest

A Test Environment for HTTP Requests

save_response function

logical: if <code>TRUE</code> (default), JSON responses with status 200
will be written as just the text of the response body. In all other cases,
and when <code>simplify</code> is <code>FALSE</code>, the "response" object will be written out to
a .R file using <code><a rd-options='base:dput' href='base::dput()'>base::dput()</a></code>.

save_response: Write out a captured response

Description

Usage

Arguments

Value