Handbook

Live Granite integration tests

Some tests exercise live OpenAI-compatible gateways (often IBM Granite or customer-hosted equivalents). They are marked @pytest.mark.granite and skip by default when required environment variables are absent.

Updated

Rules

  • Do not commit .env files, bearer tokens, or internal URLs.
  • Treat latency, quota, and context-window outcomes as deployment-specific—benchmarks are indicative, not guarantees.
  • Prefer fake_chat examples for learning paths; Granite runs belong in gated CI or maintainer machines only.

Typical variables

Exact names follow your deployment profile—consult pytest.ini markers and test modules under tests/integration/ when present. Empty or placeholder values should keep tests skipped.

Commands

# default offline suite (Granite tests excluded via pytest addopts: -m "not granite")
pytest -q

# opt-in when credentials are present on your workstation
pytest -q -m granite

See also