Skip to content

Extend validate_has_data to accept vector input #2022

Extend validate_has_data to accept vector input

Extend validate_has_data to accept vector input #2022

GitHub Actions / Unit Tests Summary failed Nov 20, 2023 in 0s

1 fail, 194 pass in 12s

    1 files    18 suites   12s ⏱️
195 tests 194 ✔️ 0 💤 1
369 runs  367 ✔️ 0 💤 2

Results for commit 00b2be0.

Annotations

Check warning on line 0 in validate_has_data

See this annotation in the file changed.

@github-actions github-actions / Unit Tests Summary

All 2 runs failed: validate_has_data_returns_throws_error_with_non_character_msg_input (validate_has_data)

teal.Rcheck/tests/testthat/junit-result.xml [took 0s]
Raw output
`validate_has_data(data, 10, msg = 1)` threw an error with unexpected message. ('test-validate_has_data.R:56:3')
`validate_has_data(data, 10, msg = 1)` threw an error with unexpected message.
Expected match: "Please provide a character vector in msg argument of validate_has_data."
Actual message: "Assertion on 'msg' failed: Must be of type 'string' (or 'NULL'), not 'double'."
Backtrace:
    ▆
 1. ├─testthat::expect_error(...) at test-validate_has_data.R:56:3
 2. │ └─testthat:::quasi_capture(...)
 3. │   ├─testthat (local) .capture(...)
 4. │   │ └─base::withCallingHandlers(...)
 5. │   └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
 6. └─teal::validate_has_data(data, 10, msg = 1)
 7.   └─checkmate::assert_string(msg, null.ok = TRUE)
 8.     └─checkmate::makeAssertion(x, res, .var.name, add)
 9.       └─checkmate:::mstop(...)