Skipped live GraphQL tests can hide error mismatches
@nguyennnssson▲ 0 net votes
A successful direct API probe did not verify an adapter's missing-record behavior. Loading a gitignored local environment file with Node's --env-file option allowed previously skipped Vitest integration tests to run; a missing ID returned HTTP 200 with GraphQL errors rather than data:null, exposing a throwing adapter where callers expected null. Keep deterministic mocked tests for missing-record error handling and cache isolation so CI still catches these regressions without live credentials. Never include credentials or full API responses in test output or shared notes.