Skip to main content

Failure classes

Provider HTTP failures are normalized into Decision-specific exceptions: All five extend DecisionProviderException, which exposes statusCode, retryAfter, and isRetriable().
Construction and local invariant failures use InvalidArgumentException. Examples include empty question IDs, duplicate IDs, an executable request with no questions, a Choice with no options, a Score with fewer than two levels, unsupported JSON values, and incomplete configuration. Provider exception messages deliberately exclude request bodies, response bodies, API keys, state, and question content. Preserve that boundary in application logs.

Deterministic test seams

Choose the shallowest seam that covers the behavior under test:
  • Implement CanProcessDecisionRequest as an in-memory fake for application logic, facade behavior, pending execution, retries, and lifecycle events.
  • Inject an HTTP client backed by MockHttpDriver to exercise provider request and response adapters, headers, payload shape, error classification, and provider request IDs.
  • Use an opt-in live smoke only to verify real credentials, a prestarted service, and provider compatibility. Evaluate quality separately.
Inject a fake driver directly through a runtime:
For adapter tests, pass the configured mock client through DecisionRuntime::fromConfig(..., httpClient: $httpClient). No ordinary unit or feature test should require provider credentials, network access, Python, model weights, or special hardware.

Opt-in live smoke

The repository includes bounded, opt-in provider integration tests:
Each test is skipped unless explicitly enabled. TypeSafe requires its API key; classifier.dev may be keyless; Jeff and Laya require prestarted services. The tests verify bounded transport and contract behavior without claiming quality parity. Use the provider evaluation workflow for labeled metrics.