paymentsdb: make specific kv store tests only available via build tag
What the developer wrote
Authored by ziggie
paymentsdb: make specific kv store tests only available via build tag
What changed, and why it matters
This commit only adds a Go build tag to a test file so that certain key-value store tests run only when neither SQLite nor PostgreSQL test modes are active. It is a test-configuration change with no effect on production code, user-facing behavior, or security.
No security action needed. Treat as a normal test-suite maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a single //go:build !test_db_sqlite && !test_db_postgres constraint to payments/db/kv_store_test.go. This gates the existing KV store tests to the default/bbolt backend test configuration and prevents them from compiling/running under the SQLite or Postgres test build variants. No runtime logic, interfaces, or production paths are modified.
Changed components
payments/db/kv_store_test.goInspect captured patch +2 / −0
diff --git a/payments/db/kv_store_test.go b/payments/db/kv_store_test.go
index ee28e12..f0c2b14 100644
--- a/payments/db/kv_store_test.go
+++ b/payments/db/kv_store_test.go
@@ -1,3 +1,5 @@
+//go:build !test_db_sqlite && !test_db_postgres
+
package paymentsdb
import (
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.