testthat

Check reporter: 13 line summary of problems

Test reporter: start recovery.

Test reporter: fail at end.

Test reporter: summary of errors in jUnit XML format.

List reporter: gather all test results along with elapsed time and file information.

Test reporter: location

Test reporter: minimal.

Multi reporter: combine several reporters in one.

Test reporter: interactive progress bar of errors.

Test reporter: RStudio

Manage test reporting

Test reporter: gather all errors silently.

Test reporter: stop on error.

Test reporter: summary of errors.

Test reporter: TAP format.

Test reporter: Teamcity format.

Watches code and tests for changes, rerunning tests as appropriate.

Watches a package for changes, rerunning tests as appropriate.

Capture conditions, including messages, warnings, expectations, and errors.

Capture output to console

Provide human-readable comparison of two objects

Compare two directory states.

Does code return a number greater/less than the expected value?

Describe the context of a set of tests.

Start test context from a file name

Retrieve the default reporter

describe: a BDD testing language

Capture the state of a directory.

Does code return the expected value?

Evaluate a promise, capturing all types of output.

The building block of all expect_ functions

Is an object equal to the expected value, ignoring attributes?

Does code throw an error, warning, message, or other condition?

Does code return a visible or invisible object?

Does an object inherit from a given class?

Expectations: is the output or the value equal to a known good value?

Does code return a vector with the specified length?

Deprecated numeric comparison functions

Does a string match a regular expression?

Does code return a vector with (given) names?

Does code return NULL?

Does code print output to the console?

Expectations: is the output or the value equal to a known good value?

Does code return a reference to the expected object?

Does code return a vector containing the expected values?

Does code execute silently?

Snapshot testing

Snapshot testing for whole files

Tools for testing expectations

Expect that a condition holds.

Does code return a vector with the expected size and/or prototype?

Construct an expectation object

Default expectations that always succeed or fail.

Find reporter object given name or object.

Find test files

Does code return an object inheriting from the expected base type, S3 class, or S4 class?

Is an error informative?

Determine testing status

Temporarily change the active testthat edition

Instantiate local snapshotting context

Locally set options for maximal test reproducibility

Locally set test directory options

Does code return TRUE or FALSE?

Make an equality test.

Negate an expectation

Old-style expectations.

Quasi-labelling

Objects exported from other packages

Get and set active reporter.

Do C++ tests past?

Compute a digest of a filename, returning NA if the file doesn't exist.

Skip a test

Snapshot management

Source a file, directory of files, or various important subsets

Does code take less than the expected amount of time to run?

Run code before/after tests

Run code after all test files

Run all tests in a directory

Generate default testing environment.

Test package examples

Run all tests in a single file

Run all tests in a package

Locate file in testing directory.

Create a test.

An R package to make testing fun!

Retrieve paths to built-in example test files

Create a testthat_results object from the test results as stored in the ListReporter results field.

Try evaluating an expressing multiple times until it succeeds.

Use Catch for C++ Unit Testing

Verify output

Watch a directory for changes (additions, deletions & modifications).

Mock functions in a package.