local_mocked_bindings

with_mocked_bindings

<a href="https://lifecycle.r-lib.org/articles/stages.html#experimental"><img src="figures/lifecycle-experimental.svg?package=testthat&version=3.1.7" alt="[Experimental]"></a>
These functions represent a second attempt at bringing mocking to testthat,
incorporating what we've learned from the mockr, mockery, and mockthat package.
<code>with_mocked_bindings()</code> and <code>local_mocked_bindings()</code> work by temporarily
changing variable bindings in the namespace of namespace <code>.package</code>.
Generally, it's only safe to mock packages that you own. If you mock other
packages, we recommend using <code>skip_on_cran()</code> to avoid CRAN failures if the
implementation changes.
These functions do not currently affect registered S3 methods.

Software testing is important, but, in part because it is
frustrating and boring, many of us avoid it. 'testthat' is a testing
framework for R that is easy to learn and use, and integrates with
your existing 'workflow'.

Hadley Wickham

testthat

Unit Testing for R

RStudio 

R Core team 

local_mocked_bindings function

<dl><dt>...</dt>
<dd>Name-value pairs providing functions to mock.</dd>
<dt>.package</dt>
<dd>The name of the package where mocked functions should be
inserted. Generally, you should not need to supply this as it will be
automatically detected when whole package tests are run or when there's
one package under active development (i.e. loaded with
<code><a href="/link/pkgload%3A%3Aload_all()?package=testthat&version=3.1.7" data-mini-rdoc="testthat::pkgload::load_all()">pkgload::load_all()</a></code>).</dd>
<dt>.env</dt>
<dd>Environment that defines effect scope. For expert use only.</dd>
<dt>code</dt>
<dd>Code to execute with specified bindings.</dd></dl>

Arguments

<a href='https://lifecycle.r-lib.org/articles/stages.html#experimental'><img src='figures/lifecycle-experimental.svg' alt='[Experimental]' /></a>
These functions represent a second attempt at bringing mocking to testthat,
incorporating what we've learned from the mockr, mockery, and mockthat package.
<code>with_mocked_bindings()</code> and <code>local_mocked_bindings()</code> work by temporarily
changing variable bindings in the namespace of namespace <code>.package</code>.
Generally, it's only safe to mock packages that you own. If you mock other
packages, we recommend using <code>skip_on_cran()</code> to avoid CRAN failures if the
implementation changes.
These functions do not currently affect registered S3 methods.

Mocking tools — local_mocked_bindings

<dl>

<dt>...</dt>
<dd>Name-value pairs providing functions to mock.</dd>


<dt>.package</dt>
<dd>The name of the package where mocked functions should be
inserted. Generally, you should not need to supply this as it will be
automatically detected when whole package tests are run or when there's
one package under active development (i.e. loaded with
<code><a href='https://rdrr.io/pkg/pkgload/man/load_all.html'>pkgload::load_all()</a></code>).</dd>


<dt>.env</dt>
<dd>Environment that defines effect scope. For expert use only.</dd>


<dt>code</dt>
<dd>Code to execute with specified bindings.</dd>

</dl>

local_mocked_bindings: Mocking tools

Description

Usage

Arguments