-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade testthat
to use 3rd edition
#656
Comments
I think we already do this right @nikolas-burkoff ? |
We have if the DESC file has |
I think it is worth it. Error messages with waldo are much more informative and warnings are better handled. Is testthat at version >3 on our platforms @arkadiuszbeer ? If so I suggest to complete this |
@Melkiades yes, we are using |
I was wondering what should we do in case of warnings. ATM it does return the warning and not the output. For example:
Should I make a wrapper of expect_warning like custom_expect_warning that preserves the old behavior with a double call or checking the piece twice in the test itself? I do not see other solutions |
btw there are hundreds of errors :D |
talking with @shajoezhu and due to the amount of work needed to fix this, we put it back to the stack to be dealt with during next increment |
From https://github.com/insightsengineering/coredev-tasks/issues/154
Part of insightsengineering/NEST-roadmap#65
The text was updated successfully, but these errors were encountered: