How do I test hapi routes without server.inject?

Record the running server with Keploy. Requests arrive over a real socket and enter the lifecycle at onRequest, so every registered plugin, auth strategy, and Joi schema executes — none of it assembled by the test.

Does the hapi request lifecycle run under Keploy?

Yes, in full. onRequest through onPreResponse all execute, route prerequisites resolve, and response shaping applies — which is what a handler called directly with a fabricated request skips.

Can Keploy test Joi validation failures?

Yes. Record a request with an invalid payload and the failAction response is captured exactly as hapi produced it, so the error contract clients rely on becomes part of the suite.

Can Keploy mock database calls in hapi?

Yes. Capture happens at the wire protocol beneath the driver, so node-postgres, mongoose, and Catbox-backed caches all replay with the data they actually returned.

Is Keploy free for hapi projects?

Yes. The Keploy CLI is open source under Apache 2.0 and free to run on any hapi service with no seat limits. It is not an npm package, so it never appears in package.json.

Keploy as a hapi testing framework

Keploy tests hapi applications by recording real requests through the running server and every database or outbound call they trigger, then replaying both as assertions. Lifecycle extensions, Joi validation, and auth strategies all execute over a real socket.

Generate hapi tests free

keploy record -c "node dist/server.js"

18.4K+

1.2M+300M+mocks createdSlack

What Keploy gives a hapi team

Any hapi app, unchanged

Keploy runs your real entrypoint, so registered plugins, route prerequisites, and auth strategies all execute. Capture is at the socket rather than inside the server object.

hapi 20 and above
Plugins and route prerequisites
Joi validation runs for real
Auth strategies genuinely exercised

Try Keploy for free Explore the docs

The problem

Why hapi integration tests slow teams down

The friction is rarely the assertions. It is everything around them — spinning up dependencies, keeping mocks honest, and repairing tests after every refactor.

Book a call Explore the docs

Three ways to do it

Testing hapi: by hand, with Jest + supertest + nock, or with Keploy

server.inject enters the lifecycle of a server the test file assembled, so plugins from your entrypoint are missing. Keploy records the real process, so nothing is absent.

By hand

Jest + supertest + nock

With Keploy

Select any row for the full comparison, with code.

Get started Book a call

Same coverage, three costs

What you write for hapi vs what Keploy records

All three produce the same assertion. Only the third still passes after the next refactor without anyone editing it.

By hand2–4 hours

confirm.test.js

hand-written

// Hand-written: the handler is called past the lifecycle.

const { confirm } = require('../src/handlers/orders');

test('confirms an authorized order', async () => {

const request = {

params: { id: 'ord_1' },

payload: { paymentToken: 'tok_123' },

// Prerequisites never ran, so this is invented.

pre: { order: { id: 'ord_1', amountMinor: 4200, state: 'NEW' } },

server: { app: { db: fakeDb, payments: fakePayments } },

};

const result = await confirm(request, fakeToolkit);

expect(result.state).toBe('CONFIRMED');

});

request.pre is fabricated, so the prerequisite that would have loaded the order — and any authorisation it performs — never ran.

Jest + supertest + nock1–2 hours

confirm.inject.test.js

tool-assisted

// Lab + server.inject + nock.

const nock = require('nock');

test('confirms an authorized order', async () => {

nock('https://api.payments.example.com')

.post('/v1/payment_intents/tok_123/confirm')

.reply(200, { status: 'AUTHORIZED' });

const server = Hapi.server();

await server.register(ordersPlugin);

// The auth strategy and logging plugin from server.js are not here.

const res = await server.inject({

method: 'POST',

url: '/orders/ord_1/confirm',

payload: { paymentToken: 'tok_123' },

});

expect(res.statusCode).toBe(200);

});

The lifecycle runs, which is the right idea — and it is the lifecycle of a server assembled here, so the auth strategy your entrypoint registers is missing.

With Keploy~5 minutes

test-1.yaml

auto-generated

# Recorded with: keploy record -c 'node dist/server.js'

# Nobody wrote this file. Keploy captured it from a real request.

version: api.keploy.io/v1beta1

kind: Http

name: test-1

spec:

req:

method: POST

url: /orders/ord_1/confirm

header:

Authorization: Bearer <captured>

body: '{"paymentToken":"tok_123"}'

resp:

status_code: 200

body:

id: "ord_1"

state: "CONFIRMED"

amountMinor: 4200

noise:

- body.confirmedAt

mocks:

- kind: Postgres

operation: "SELECT id, amount_minor, state FROM orders WHERE id = $1"

- kind: Http

url: https://api.payments.example.com/v1/payment_intents/tok_123/confirm

The recorded case entered the lifecycle at onRequest and passed the real auth strategy and Joi validation before reaching the handler.

Times are estimates for authoring one endpoint’s coverage from scratch, not measurements.

Explore the docs Request a trial

Keploy vs the alternatives

hapi testing tools, compared

The options a team on Node.js actually reaches for, and where each one genuinely wins. Select a row for the full comparison.

Keploy

Jest + supertest

nock

Mocha + Sinon

Mock Service Worker

Postman

SmartBear ReadyAPI

Best in classStrongPartialNot covered

Assessments reflect each tool’s documented behaviour, not benchmark measurements.

Request a trial Book a call

How it works

Record your hapi app once, replay it forever

Keploy sits below your hapi process at the network layer. It watches the calls your app already makes, then serves them back on replay so tests run with no dependencies attached.

Your hapi appGET/api/v1/orders/{id}200

RecordingKeploy proxyeBPF · userspace

PostgreSQLPostgres frontend/backend protocol

MySQLMySQL wire protocol

MongoDBMongoDB wire protocol

RedisRESP over TCP

+3 more hapi dependencies

An example shape of a captured call. Your own endpoints and dependencies come from your real traffic, so nothing here has to be written by hand.

Try Keploy for free Request a trial

Mock coverage

What Keploy mocks for hapi, with zero config

7 of the 7 dependencies a typical hapi service talks to are stubbed from the recording itself — no mock classes, no fixture files, no containers in CI.

Auto-mocked
PostgreSQLView page
Postgres frontend/backend protocol
Auto-mocked
MySQLView page
MySQL wire protocol
Auto-mocked
MongoDBView page
MongoDB wire protocol
Auto-mocked
RedisView page
RESP over TCP
Auto-mocked
Apache KafkaView page
Kafka producer and consumer protocol
Auto-mocked
gRPCView page
HTTP/2 framed gRPC calls
Outbound HTTP
Auto-mocked
Outbound HTTP
Any HTTP client call the service makes

Explore the docs Book a call

Quick start

Your first hapi test suite in under five minutes

Every command below runs against your existing hapi service. Nothing in your source tree changes.

1
1Install the Keploy CLI
A single binary. It needs a Linux kernel with eBPF support, or Docker on macOS and Windows — and it adds nothing to your project's dependencies.
curl -sSL https://keploy.io/install.sh | bash
2
2Record your service
Pass the command you already use to start the app. Keploy runs it and watches every socket it opens.
keploy record -c "node dist/server.js"
3
3Exercise the paths you care about
Drive the running server. Every request becomes a test case with its database and HTTP calls captured alongside.
npm run build
curl -X POST localhost:3000/orders/ord_1/confirm -H 'Content-Type: application/json' -H 'Authorization: Bearer $TOKEN' -d '{"paymentToken":"tok_123"}'
4
4Replay in CI
Replay serves the recorded dependency responses, so the job needs no service containers and no Docker daemon.
keploy test -c "node dist/server.js" --delay 8