You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in a scenario where devtools::check() consistently fails at the testing suite state. However devtools::test() consistently succeeds. I need to be able to see the output from stdout and stderr to get some sort of insight into what is happening.
I am now using the DebugReporter with test_check() in my tests/testthat.R file. However this results in a test error
because the debug reporter tries to recover using utils::menu().
It would be great if there were a reporter that can be used to debug non-interactive scenarios.
Right now I have no way to debug my devtools::check() and the help from the DebugReporter is make it a bit better but also making it tougher to sift through due to the additional error.
The text was updated successfully, but these errors were encountered:
I'm in a scenario where
devtools::check()
consistently fails at the testing suite state. Howeverdevtools::test()
consistently succeeds. I need to be able to see the output from stdout and stderr to get some sort of insight into what is happening.I am now using the
DebugReporter
withtest_check()
in mytests/testthat.R
file. However this results in a test errorbecause the debug reporter tries to recover using
utils::menu()
.It would be great if there were a reporter that can be used to debug non-interactive scenarios.
Right now I have no way to debug my
devtools::check()
and the help from theDebugReporter
is make it a bit better but also making it tougher to sift through due to the additional error.The text was updated successfully, but these errors were encountered: