Is it just me, or does {bit64} and {testthat} behave unexpectdly?

In this example, {testthat} thinks that these two bit64::integer64 values are the same, and does not throw an error?

A reproduction on someone else's machine would be welcomed!

Is it because {testthat} is doing a comparison of the underlying floating point value, rather than using bit64's idea of equality?

#RStats #testthat #bit

{tetthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat

I can not remember who said it (possibly @jennybryan), but there is a refrain that goes something like "if you do not test your software, your users are the tests."

Does anyone have a source on this?

#RStats #UnitTesting #TestThat

{tetthat} is great for automatic testing. Here are some tricks for the heavy user: https://blog.r-hub.io/2020/11/18/testthat-utility-belt/ #rstats #testing #unittest #testthat