Sha256: 631c8fcbe911febec986c45058c496dd48fb4eb6928bebfda42c4392f4f43e62

Contents?: true

Size: 1.76 KB

Versions: 228

Compression:

Stored size: 1.76 KB

Contents

# Install `testthat`

Tests for this track make use of the `testthat` package.

To install the package, simply open up R and run:

`install.packages("testthat")`

You can check that the package is installed successfully by running:

`library(testthat)`

# Running Tests

Each problem will have a script named `test_<exercise-name>.R` (e.g. `test_hello-world.R`). 

To run the tests for an exercise, simply execute this R script.

In RStudio, this is as simple as opening the test script, and clicking "Source" at the top right of the source pane. This will load your solution code through the `source` command on the first line of the test script, and then execute the suite of `testthat` tests that follow.

Note however, that the `source()` command on the first line of the test script will only work if your solution script (`<exercise-name>.R`) is located in your working directory. If this is not the case, you'll need to either: 
- change your working directory eg. `setwd('exercism/R/hello-world/')`, or 
- update the first line of the test script e.g. `source('exercism/R/hello-world/test_hello-world.R')`

If you prefer, you can also run the tests from the command line with `Rscript path_to_exercise_directory/test_<exercise-name>.R` (e.g. `Rscript hello-world/test_hello-world.R`)

Another convenient way to run these tests is to make use of [testthat's `auto_test` function](https://www.rdocumentation.org/packages/testthat/topics/auto_test). Since exercism code and tests are located in the same folder, use this same path for both the `code_path` and `test_path` parameters. After running `auto_test()`, the tests for the exercise will be executed automatically each time you update/save your R code for the exercise. This can help facilitate rapid iteration while working on your solution.

Version data entries

228 entries across 228 versions & 1 rubygems

Version Path
trackler-2.2.1.180 tracks/r/docs/TESTS.md
trackler-2.2.1.179 tracks/r/docs/TESTS.md
trackler-2.2.1.178 tracks/r/docs/TESTS.md
trackler-2.2.1.177 tracks/r/docs/TESTS.md
trackler-2.2.1.176 tracks/r/docs/TESTS.md
trackler-2.2.1.175 tracks/r/docs/TESTS.md
trackler-2.2.1.174 tracks/r/docs/TESTS.md
trackler-2.2.1.173 tracks/r/docs/TESTS.md
trackler-2.2.1.172 tracks/r/docs/TESTS.md
trackler-2.2.1.171 tracks/r/docs/TESTS.md
trackler-2.2.1.170 tracks/r/docs/TESTS.md
trackler-2.2.1.169 tracks/r/docs/TESTS.md
trackler-2.2.1.167 tracks/r/docs/TESTS.md
trackler-2.2.1.166 tracks/r/docs/TESTS.md
trackler-2.2.1.165 tracks/r/docs/TESTS.md
trackler-2.2.1.164 tracks/r/docs/TESTS.md
trackler-2.2.1.163 tracks/r/docs/TESTS.md
trackler-2.2.1.162 tracks/r/docs/TESTS.md
trackler-2.2.1.161 tracks/r/docs/TESTS.md
trackler-2.2.1.160 tracks/r/docs/TESTS.md