test: skip container-backed integration tests under -short

[abhicris]

What

Gate the four Qdrant-container-backed tests on testing.Short():

• TestCollectionsClient (qdrant_test/collections_test.go)
• TestPointsClient (qdrant_test/points_test.go)
• TestSnapshotsClient (qdrant_test/snapshots_test.go)
• TestHealthCheck (qdrant_test/qdrant_test.go)

Pure-unit tests (TestParseVersion, TestIsCompatible) are untouched — they already run fine everywhere.

A small shared helper skipIfShort(t) lives alongside the container factories in image_test.go.

Why

Every container-backed entrypoint calls testcontainers.GenericContainer(...), which in turn calls testcontainers-go/internal/core.MustExtractDockerHost. On any host without a reachable Docker daemon, that function panics:

panic: rootless Docker not found [recovered, repanicked]
    github.com/testcontainers/testcontainers-go/internal/core.MustExtractDockerHost.func1()
        .../testcontainers-go@v0.40.0/internal/core/docker_host.go:91 +0x68

Reproduction on a dev workstation without Docker:

$ go test -timeout 60s ./...
--- FAIL: TestPointsClient (0.00s)
panic: rootless Docker not found [recovered, repanicked]
FAIL    github.com/hanzoai/vector-go/qdrant_test    0.626s

This makes go test ./... unusable for contributors who are iterating on non-integration code paths (compare_versions, value_map, oneof_factory, etc.) — you either install & start Docker or you can't run the suite at all.

After this patch:

$ go test -short -timeout 60s ./...
ok      github.com/hanzoai/vector-go/qdrant_test    0.604s

The normal go test ./... path is unchanged, so CI's Go Tests workflow (which doesn't pass -short) keeps running the full integration suite exactly as before. The -short flag is only opt-in.

Verified

• go test -short ./... → all packages PASS (previously: panic)
• go test -run TestIsCompatible ./qdrant_test/... → PASS (confirms pure-unit tests unaffected)
• go build ./... → clean
• go vet ./... → clean
• gofmt -l qdrant_test/ → clean on modified files

Scope

Pure test: change — no production code in qdrant/ touched. No dependency changes. No workflow changes.

---

— kcolbchain / Abhishek Krishna

[abhicris]

Heads up on the two red checks on this PR — both are pre-existing on master, not introduced by this diff:

1. lint (6s red on every master commit since Go 1.26.1 bump)

Error: can't load config: the Go language version (go1.25) used to build golangci-lint
is lower than the targeted Go version (1.26.1)

.github/workflows/golangci-lint.yml pins golangci/golangci-lint-action@v9 with version: v2.8.0 (built with Go 1.25). go.mod declares go 1.26.1 (commit 4c538bb). The linter refuses to load the config. Same root cause I fixed in hanzoai/search-go#5 earlier today — the fix there was version: v2.11.4 + setup-go 1.26. Happy to follow up with a mirror PR here if helpful; I kept this PR scope-clean so it's easy to review as a pure test: change.

2. build / Go Tests
Every failure in the integration suite is a ZAP protocol mismatch between the client and the upstream qdrant/qdrant:v1.16.1 container — e.g.:

• zap: response payload too large: 302252032 bytes
• zap: read response payload: unexpected EOF
• zap: write header: write tcp ...: broken pipe

The feat: replace gRPC with ZAP transport for all vector operations commit (503935a) changed the client's wire format to ZAP, but the Qdrant container image on port 6334 still speaks gRPC. The container never actually completes a handshake with the ZAP client, which is why every op errors out immediately (0.00s). The three PASS cases in TestCollectionsClient (CreateCollectionWithInvalidParams, UpdateNonExistentCollection, DeleteNonExistentCollection) pass because they expect errors and receive them — it's a false green.

That's a separate, much larger problem (need either a ZAP-aware Qdrant server image or a shim). Out of scope for this PR, flagging for visibility. Happy to dig into it as a follow-up if there's appetite.

The contribution of this PR: a dev trying to run go test -short ./... on a laptop without Docker can now actually do so. Before this PR: Docker-host-not-found panic. After this PR: the unit tests (TestParseVersion, TestIsCompatible) run and pass, integration tests skip cleanly.

— kcolbchain / Abhishek Krishna