Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
CRAN check status Build status Build status Build status Coverage Status Life cycle: maturing R Consortium: ISC Project 2017-2

future.tests: Test Suite for 'Future API' Backends

The future package defines the Future API which consists of a small number of functions for writing R code that can be evaluated either sequential or in parallel based a single setting without having to change anything in the code. Parallelization can be done via one of many backends, e.g. via built-in multicore, multisession and cluster backends (based on the parallel package) or via third-party backends such as future.callr and future.batchtools. The design motto of the Future API is:

Write once, run anywhere

In order for such code to work regardless of which future backend the end-user choose, it is critical that the backend fully complies with the Future API. A future backend with A 100% compliance rate guarantees that the code will work equally well there as in sequential mode.

This R package - future.tests - provides a test suite for validation that a future backend complies with the Future API.

Validate a Future Backend

All future backends implementing the Future API should validate that they conform to the Future API. This can be done using the future.tests package, which provides two API for running the tests. The tests can be performed either from within R or from outside of R from the command line making it easy to include them package tests and in Continuous Integration (CI) pipelines.

From Within R

> results <- future.tests::check(plan = "multisession")
> exit_code <- attr(results, "exit_code")
> if (exit_code != 0) stop("One or more tests failed")

From Outside R

$ Rscript -e "future.tests::check" --args --test-plan="multisession"
$ exit_code=$?
$ [[ exit_code -eq 0 ]] || { >&2 echo "One or more tests failed"; exit 1; }

Continuous Integration

Travis CI

To validate a future backend using future.tests on Travis CI, use a job matrix and add a separate job that runs Rscript future.tests::check .... Here is an excerpt of a .travis.yml with a job matrix where one of the job performs a regular R CMD check --as-cran and one validates a specific backend using future.tests.

language: r
sudo: false
cache: packages
warnings_are_errors: false
r_check_args: --as-cran

    - os: linux
      r: release
    - os: linux
      r: release
        - future.tests
        - R CMD build --no-build-vignettes --no-manual .
        - R CMD INSTALL *.tar.gz
        - Rscript -e future.tests::check --args --test-plan="${BACKEND}"
      env: BACKEND='future.callr::callr'

See .travis.yml of the future.callr package for a full example.


R package future.tests is available on CRAN and can be installed in R as:


Pre-release version

To install the pre-release version that is available in Git branch develop on GitHub, use:

remotes::install_github("HenrikBengtsson/future.tests", ref="develop")

This will install the package from source.


To contribute to this package, please see


🔩 R package: future.tests - Test Suite for Future API Backends




No packages published