Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upTests fail for me #170
Tests fail for me #170
Comments
|
You're right ... it's definitely not set up for people other than me to run the tests. You're the first person who has wanted to. Will work on it. Here's the build section of .Rproj:
I had not committed that because the library is hard-wired to something specific to me and I didn't know if it was worse to provide or not? |
|
Oh, ok. I didn't know if you were doing anything fancy in Obviously no rush on this. I was just going to whittle away at the |
also represents a very small step towards resolving #170
also represents a very small step towards resolving #170
also represents a very small step towards resolving #170
Depending on how I test the package, I get different failures.
testthat::test_packageproduces a smaller set.devtools::test()fails all but the last authorization test, etc.At the very least, it looks like the expectations around
user_infointest-auth.Rwill be problematic.Additionally, access to the private sheet in
test-consume-data-private.Ris problematic for anyone for whom you haven't granted access.IMHO it's understandable if this particular package requires some additional love to get the tests working. But a "Development" section in the readme that documents what needs to be done would be neat.
And/or if you're willing to be proprietary, checking in the .Rproj file with the build flags you use would be convenient.