Question 1

How to redact API keys from go-vcr cassettes?

Accepted Answer

Use the BeforeSaveHook to modify interactions before saving. For example, delete headers like Authorization or replace response bodies with placeholder text, as shown in the README's hook examples.

Question 2

Can go-vcr handle HTTP/2 or WebSocket connections?

Accepted Answer

No, go-vcr is designed for standard HTTP/1.x interactions and does not natively support HTTP/2 or WebSockets, so it's not suitable for testing modern protocol-based services.

Question 3

What's the best way to update cassettes when an API changes?

Accepted Answer

You'll need to re-record the cassettes by running tests in recording mode again. This involves deleting old cassettes or using passthrough options to update specific interactions, which can be time-consuming.

Question 4

How does go-vcr compare to using httptest for mocking HTTP responses?

Accepted Answer

go-vcr records actual HTTP interactions for realism and determinism, ideal for integration tests, while httptest requires manual mock setup and offers more control for unit tests but less automation.

Question 5

How to integrate go-vcr with table-driven tests in Go?

Accepted Answer

Create a new recorder for each test case or use a shared recorder with custom matchers. Name cassettes uniquely, often using test names, to avoid conflicts and ensure accurate playback.

Question 6

Is go-vcr suitable for testing GraphQL APIs?

Accepted Answer

Yes, but you need custom matchers to handle GraphQL request bodies, as default matchers might not account for query variations. Hooks can help redact sensitive data in responses.

go-vcr

What is go-vcr?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions