search

rstudio / vetiver-r

Version, share, deploy, and monitor models
https://rstudio.github.io/vetiver-r/
Other
181 stars 27 forks source link

Write tests for more types of boards, not just `board_temp()` #258

Closed juliasilge closed 10 months ago

juliasilge commented 10 months ago

In #257 I wrote:

I need to think about testing across different board types in vetiver. The pins package is tested very extensively across all the backends but vetiver does not, and here it is the code that vetiver ran that was the problem. I could probably get away with mocking vetiver_pin_read() in such tests to avoid needing to call S3 like pins CI does.

To get this to work, I need to export new_board() from pins. Then I can mock creating boards like board_s3() and board_url() and write tests to make sure that the code in vetiver behaves as expected.