Refactor tests to use snapshots and abort_bad_argument()
#50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here are a couple extra suggestions when trying to improve error messages.
I highly recommend using snapshot tests, as you can quickly verify that your output changed how you want it.
It is better to add a
call
argument toabort_bad_argument()
to make testing easierexpect_snapshot(error = TRUE)
is a lifesaver https://testthat.r-lib.org/articles/snapshotting.htmlAlso discovered that
abort()
/cli_abort()
have a dedicated argument to take care of extra info:footer
, so renamed it to this (and ifcustom
, don't showfooter
)custom
requiresmust
to be optional.Edit: made a mistake in the first place that I easily caught with snapshot tests! e8d8868 It is easier to experiment this way