conjunct_test_linter

For readability of test outputs, testing only one thing per call to
<code><a href="https://testthat.r-lib.org/reference/logical-expectations.html">testthat::expect_true()</a></code> is preferable, i.e.,
<code>expect_true(A); expect_true(B)</code> is better than <code>expect_true(A &amp;&amp; B)</code>, and
<code>expect_false(A); expect_false(B)</code> is better than <code>expect_false(A || B)</code>.

Checks adherence to a given style, syntax errors and possible
semantic issues.  Supports on the fly checking of R code edited with
'RStudio IDE', 'Emacs', 'Vim', 'Sublime Text', 'Atom' and 'Visual
Studio Code'.

Jim Hester

lintr

A 'Linter' for R Code

Florent Angly

Russ Hyde

Michael Chirico

Kun Ren

Alexander Rosenstock

Indrajeet Patil

conjunct_test_linter function

<dl><dt>allow_named_stopifnot</dt>
<dd>Logical, <code>TRUE</code> by default. If <code>FALSE</code>, "named" calls to <code><a href="/link/stopifnot()?package=lintr&version=3.0.2" data-mini-rdoc="lintr::stopifnot()">stopifnot()</a></code>,
available since R 4.0.0 to provide helpful messages for test failures, are also linted.</dd></dl>

Arguments

best_practices, package_development, readability

Force &amp;&amp; conditions in expect_true(), expect_false() to be written separately — conjunct_test_linter

<dl>

<dt>allow_named_stopifnot</dt>
<dd>Logical, <code>TRUE</code> by default. If <code>FALSE</code>, "named" calls to <code><a href='https://rdrr.io/r/base/stopifnot.html'>stopifnot()</a></code>,
available since R 4.0.0 to provide helpful messages for test failures, are also linted.</dd>

</dl>

conjunct_test_linter: Force && conditions in expect_true(), expect_false() to be written separately

Description

Usage

Arguments

Tags

Details

See Also