Title: Help for Writing Unit Tests Based on Function Examples
Imports: filesstrings, magrittr, stringr, BBmisc, devtools, formatR,

person("Sergi", "Padilla-Parra", email = "spadilla@well.ox.ac.uk", role = "ths"))
Imports: filesstrings (>= 1.1.0), magrittr, stringr, devtools, formatR,

Imports: filesstrings (>= 1.2.0), magrittr, stringr, devtools, formatR,

Imports: filesstrings (>= 1.2.0), magrittr, stringr, devtools, styler,

Imports: filesstrings (>= 2.2.0), magrittr, stringr, devtools, styler,
purrr, roxygen2, checkmate, readr, utils, ore, rprojroot

Imports: filesstrings (>= 2.5.0), magrittr, stringr, devtools, styler
(>= 1.0.2), purrr, roxygen2, checkmate, readr, utils, ore,

Imports: filesstrings (>= 2.7.0), magrittr, stringr, devtools, styler
(>= 1.0.2), purrr, roxygen2, checkmate, readr, utils, ore (>=
1.4.0), rprojroot, usethis, clisymbols, crayon, fs, glue, rlang

Imports: filesstrings (>= 3.0.0), magrittr, stringr, styler (>= 1.0.2),
purrr, roxygen2, checkmate, readr, utils, ore (>= 1.4.0),
rprojroot, usethis, clisymbols, crayon, fs, glue, rlang
Suggests: testthat, covr, knitr, rmarkdown, spelling, pacman

the user) of test files to be tested with the 'testthat' package. Sort of
Imports: filesstrings (>= 3.1.5), magrittr (>= 1.5), stringr (>=
1.2.0), styler (>= 1.1.1), purrr, roxygen2, checkmate (>=
Suggests: testthat (>= 2.1.0), covr, knitr, rmarkdown, spelling,

Description: Take the examples written in your documentation of
functions and use them to create shells (skeletons which must be
manually completed by the user) of test files to be tested with the
'testthat' package. Sort of like python 'doctests' for R.
readr, rlang (>= 0.3.3), roxygen2, stringr (>= 1.2.0), styler
Suggests: covr, crayon, knitr, pacman, rmarkdown, spelling, testthat

Imports: checkmate (>= 1.9.3), clipr (>= 0.7.0), filesstrings (>=
purrr, readr, rlang (>= 0.3.3), roxygen2, rstudioapi (>= 0.4),

magrittr (>= 1.5), ore (>= 1.4.0), purrr, readr, rlang (>=
Suggests: clipr (>= 0.7.0), covr, crayon, knitr, pacman, rmarkdown,