Skip to content

Testing integrations

The SDK repository includes unit tests that use a custom HttpMessageHandler, so tests do not need a live Okatana deployment.

Run:

dotnet test Okatana.sln

The suite verifies URL configuration, authentication headers, request serialization, explicit-null PATCH behavior, status-to-exception mapping, safe-read retries, no default POST retry, Laravel pagination, cross-origin pagination rejection, OpenAPI operation coverage, and execution of all 30 typed endpoint methods.

Integration test checklist

Before production rollout, test against a non-production Okatana deployment:

  • a correctly scoped read succeeds;
  • missing or bad credentials return 401;
  • a missing scope returns 403;
  • invalid relationship IDs return the documented 404/422 class;
  • create/update/delete actions appear in audit history as the integration actor;
  • token revocation takes effect;
  • rate limiting behaves as expected;
  • pagination can traverse more than one page;
  • any configured webhook receives intended events.

Keep integration-test credentials separate from production keys.