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

new behavior of suppressing messages and warnings in tests is wrong #254

Closed
kforner opened this Issue May 6, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@kforner
Contributor

kforner commented May 6, 2015

Because:

  1. warnings can be very useful to detect bugs in the tests and in the code to be tested
    If you want to get rid of some (once you understand them, just suppress them using suppressMessages or suppressWarnings, or better test them using expect_warning

  2. now it is impossible to test code that deals with warnings. For instance suppose that you want to test a function that turns warnings into errors using the warn=2 option, it does no longer work in testthat tests.

  3. code does not behave like in the real R world.

just my opinion.

@hadley

This comment has been minimized.

Member

hadley commented Sep 24, 2015

Hmmm, I think that ignoring messages is the right thing to do (in the same way printed output is ignored), but ignoring warnings might be too much.

@kforner

This comment has been minimized.

Contributor

kforner commented Sep 24, 2015

Agreed.

@hadley hadley modified the milestone: 0.11.0 Sep 29, 2015

@hadley hadley closed this in 6403639 Sep 29, 2015

@kforner

This comment has been minimized.

Contributor

kforner commented Sep 29, 2015

great !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment