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
Now that we are on GitHub and happily, transparently public, we can use Travis for continuous integration and running tests. For instance, in the issue I just posted #16 , the call is failing for my particular DF but succeeding for a toy example with mtcars. It would be nice to test both cases once we figure out what's going on there.
The text was updated successfully, but these errors were encountered:
I see we already have testthat setup, and tests for some functions! I'm setting up Travis CI integration. I don't think codecov is crucial, as long as Travis breaks when any test fails, but it would be a nice-to-have.
Our Travis builds might be slow b/c of all the dependencies this package installs.
Now that we are on GitHub and happily, transparently public, we can use Travis for continuous integration and running tests. For instance, in the issue I just posted #16 , the call is failing for my particular DF but succeeding for a toy example with mtcars. It would be nice to test both cases once we figure out what's going on there.
The text was updated successfully, but these errors were encountered: