https://github.com/datacamp/testwhat.ext
extensions (high-level SCTs) for testwhat
https://github.com/datacamp/testwhat.ext
fs le
Last synced: 2 months ago
JSON representation
extensions (high-level SCTs) for testwhat
- Host: GitHub
- URL: https://github.com/datacamp/testwhat.ext
- Owner: datacamp
- License: agpl-3.0
- Created: 2017-06-22T16:18:06.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2022-08-26T07:51:01.000Z (almost 4 years ago)
- Last Synced: 2025-03-05T09:16:26.974Z (over 1 year ago)
- Topics: fs, le
- Language: R
- Homepage: https://datacamp.github.io/testwhat.ext/
- Size: 144 KB
- Stars: 0
- Watchers: 29
- Forks: 1
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
> :warning: **This repo has outdated tokens in its travisci config**
> To make new releases for this project it needs to be moved to circleci
# testwhat.ext
[](https://travis-ci.org/datacamp/testwhat.ext)
[](https://codecov.io/gh/datacamp/testwhat.ext)
[](https://app.fossa.io/projects/git%2Bgithub.com%2Fdatacamp%2Ftestwhat.ext?ref=badge_shield)
Extensions for testwhat for specific use-cases or more high level checks. Documentation can be found [here](https://datacamp/github.io/testwhat.ext).
To use the extensions in the submission correctness tests for an exercise, explicitly load the package before you use the function:
```R
library(testwhat.ext)
ex() %>% check_cpp_function_exported("int", "answer")
```
## Adding SCTs to testwhat.ext
Follow these steps
1. Open a PR, merge into master when appropriate.
2. Once merged, edit DESCRIPTION, incrementing `VERSION: 0.0.1` to reflect changes ([see semver for guidance](http://semver.org/)).
3. Create a github release labeled `vVERSION`. E.g. `v0.0.1`. (see [here](https://help.github.com/articles/creating-releases/)).
## License
[](https://app.fossa.io/projects/git%2Bgithub.com%2Fdatacamp%2Ftestwhat.ext?ref=badge_large)