How the proper way to use RubyLLM in tests? #461
-
|
I don´t like the idea of VCR in my integration specs (cucumber) and cannot afford the idea of open requests to another services, and again the high risk of expose the keys, have any plan to support a common facility to made the tests more easy? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Short answer: no. RubyLLM is a real library that has to work against real APIs in the real world. VCR is the right path because it records those real interactions and keeps tests deterministic afterward. Recording cassettes does require paying for real API calls sometimes. That tradeoff is expected, and we accept it. On key exposure: use VCR filtering/scrubbing. That’s exactly what it’s for. There are no plans to add a separate testing facility for this. |
Beta Was this translation helpful? Give feedback.
Short answer: no.
RubyLLM is a real library that has to work against real APIs in the real world. VCR is the right path because it records those real interactions and keeps tests deterministic afterward.
Recording cassettes does require paying for real API calls sometimes. That tradeoff is expected, and we accept it.
On key exposure: use VCR filtering/scrubbing. That’s exactly what it’s for.
There are no plans to add a separate testing facility for this.