A Test Environment for Database Requests

Testing and documenting code that communicates with remote databases can be painful. Although the interaction with R is usually relatively simple (e.g. data(frames) passed to and from a database), because they rely on a separate service and the data there, testing them can be difficult to set up, unsustainable in a continuous integration environment, or impossible without replicating an entire production cluster. This package addresses that by allowing you to make recordings from your database interactions and then play them back while testing (or in other contexts) all without needing to spin up or have access to the database your code would typically connect to.


Reference manual

It appears you don't have a PDF plugin for this browser. You can click here to download the reference manual.


0.1.3 by Jonathan Keane, a year ago

https://dittodb.jonkeane.com/, https://github.com/ropensci/dittodb

Report a bug at https://github.com/ropensci/dittodb/issues

Browse source code at https://github.com/cran/dittodb

Authors: Jonathan Keane [aut, cre] , Mauricio Vargas [aut] , Helen Miller [rev] (reviewed the package for rOpenSci , see https://github.com/ropensci/software-review/issues/366) , Etienne Racine [rev] (reviewed the package for rOpenSci , see https://github.com/ropensci/software-review/issues/366)

Documentation:   PDF Manual  

Task views: Databases with R

Apache License (>= 2.0) license

Imports digest, glue, methods, testthat, utils, lifecycle

Depends on DBI

Suggests callr, covr, dplyr, dbplyr, knitr, nycflights13, odbc, RMariaDB, RPostgres, RPostgreSQL, RSQLite, spelling, withr, rmarkdown, lintr

Suggested by pointblank.

See at CRAN