Package: httptest
Type: Package
Title: A Test Environment for HTTP Requests
Description: Testing code and packages that communicate with remote servers can
be painful. Dealing with authentication, bootstrapping server state,
cleaning up objects that may get created during the test run, network
flakiness, 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 test
contexts that mock the network connection in different ways, and it offers
additional expectations to assert that HTTP requests were--or were
not--made. Using these tools, one can test that code is making the intended
requests and that it handles the expected responses correctly, all without
depending on a connection to a remote API.
Version: 1.1.0
Date: 2017-02-03
Authors@R: person("Neal", "Richardson", role=c("aut", "cre"), email="neal.p.richardson@gmail.com")
Author: Neal Richardson [aut, cre]
Maintainer: Neal Richardson <neal.p.richardson@gmail.com>
URL: https://github.com/nealrichardson/httptest
BugReports: https://github.com/nealrichardson/httptest/issues
License: MIT + file LICENSE
Depends: R (>= 3.0.0), testthat
Imports: digest, httr, jsonlite
RoxygenNote: 6.0.0
NeedsCompilation: no
Packaged: 2017-02-03 17:30:57 UTC; neal.richardson
Repository: CRAN
Date/Publication: 2017-02-03 19:08:29

Packaged: 2017-03-21 21:52:43 UTC; neal.richardson

Packaged: 2017-04-13 20:41:33 UTC; neal.richardson

Packaged: 2017-06-04 17:53:52 UTC; neal.richardson

Packaged: 2017-07-31 05:24:46 UTC; neal.richardson

Packaged: 2017-08-04 20:12:41 UTC; neal.richardson

not--made. It also allows you to record real API responses to use as mocks
in tests. With these tools, one can test that code is making the intended
Packaged: 2017-10-20 03:57:08 UTC; neal.richardson

Packaged: 2017-11-14 01:06:56 UTC; neal.richardson

Description: 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
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.
Suggests: covr, knitr, rmarkdown, spelling, xml2
Packaged: 2018-01-16 18:22:26 UTC; neal.richardson