ProtectedconstructorCreate an Adapter.
The blueprint to create the adapter.
Protected ReadonlyblueprintProtected ReadonlyhooksProtected ReadonlymiddlewareProtected ReadonlyresolvedProtectedbuildThe raw response for a test IS the outgoing response the handlers produced.
The adapter context.
The outgoing response.
ProtecteddispatchDispatch one event through the kernel and return the outgoing response.
The incoming event.
The outgoing response.
ProtectedexecuteExecute the event handler lifecycle hooks.
The hook to execute.
The event handler to be run.
ProtectedexecuteExecute adapter lifecycle hooks.
The hook's name.
Optionalcontext: TestAdapterContext
The event context.
Optionalerror: any
The error to handle.
ProtectedhandleHandle error.
The error to handle.
The event context.
The raw response.
ProtectedhandleHandle the event.
The event context.
The event handler to be run.
The raw response wrapper.
ProtectedmakeCreate pipeline options for the Adapter.
The pipeline options for transforming the event.
ProtectedonLifecycle hook run once before the first dispatch.
ProtectedresolveGet the error handler for the given error.
The error to get the handler for.
The error handler.
ProtectedresolveStart the adapter and return a test client.
The test client.
ProtectedsendSend the raw event through the destination.
The event context.
The event handler to be run.
Platform-specific response.
ProtectedvalidateValidate the context and event handler.
The context to validate.
The event handler to validate.
StaticcreateThe application blueprint.
A new adapter instance.
An in-memory adapter used only for tests.
Instead of a server,
run()returns a TestClient whosesendpushes a caller-suppliedIncomingEventstraight through the real adapter + kernel pipeline and returns the resultingOutgoingResponse. There is no request normalisation (you provide a ready event) and the raw response IS the outgoing response, so assertions see exactly what your handlers produced.