Skip to content

Testing

This section collects the hands-on guides for testing GTB. Most day-to-day work is covered by the automated suites wired into just:

Command Scope
just test Unit tests with coverage
just test-race Race detector pass
just test-integration Env-var-gated integration suites — see Integration Testing
just test-e2e Godog / BDD scenarios against the cmd/e2e binary
just test-e2e-smoke Fast subset of the E2E suite
just security govulncheck, trivy, gitleaks, osv-scanner

Some features involve external platform state (OS keychains, OAuth flows, rate-limited APIs) that the automated suites either mock out or skip. The guides in this directory cover how to exercise those paths on a real workstation, primarily for spec verification and pre-release smoke testing.

In this section

  • Manual credential testing — walk through the OS-keychain storage mode end-to-end using the cmd/e2e binary: wizard UX, runtime resolution, CI refusal, probe gating, Bitbucket JSON blob, and regulated-build stripping.
  • Testing the keychain on a headless host — three ways to unblock yourself when the dev server, CI runner, or container has no registered Secret Service: install GNOME Keyring with dbus-run-session, run a containerised Secret Service, or swap in the in-memory backend from credtest.