Open maxheld83 opened 3 years ago
I thought and read a little bit about testing against (live) APIs, also including the recent ropensci book on the topic: https://books.ropensci.org/http-testing/ Some comments on that in this PR and related issue: https://github.com/ropensci-books/http-testing/pull/91
I think generally we should:
To test, if a compliance check works, we would record the HTTP calls and responses just once and re-use them, right? Like https://github.com/ropensci/vcr
Mmh, I am not 💯sure yet, but I don't think we should be mocking anything in metacheck (as would be done via vcr).
There's basically two sets of tests relevant here:
So in summary, I don't think there's any need for mocking in metacheck. Mocking/faking also always adds a level of complexity that needs to be justified, and I don't think it is here.
This issue should still stay open until:
tests will currently ocassionally invalidate when cr data changes, and some of these changes percolate through. that is causing noise.