Skip to content
Buy me a coffee

Testing

Services take an AbortSignal parameter, so tests create one. No module needed.

it('stops when aborted', async () => {
const controller = new AbortController();
controller.abort(new AbortError('test', 'client-disconnected'));
await expect(service.list(controller.signal)).rejects.toBeInstanceOf(AbortError);
});
it('runs to the end otherwise', async () => {
await expect(service.list(new AbortController().signal)).resolves.toHaveLength(3);
});

In a controller unit test, the decorator is not involved. Pass the signal as the argument it would receive.

await controller.list(new AbortController().signal);

The middleware listens to the real response, so e2e tests need a listening server. A short timeout keeps the test fast.

@Module({
imports: [AbortControllerModule.forRoot({ timeout: 200 })],
controllers: [SlowController],
providers: [{ provide: APP_FILTER, useClass: AbortExceptionFilter }],
})
class TestModule {}
let app: INestApplication;
let port: number;
beforeAll(async () => {
app = await NestFactory.create(TestModule, { logger: false });
await app.listen(0, '127.0.0.1');
port = app.getHttpServer().address().port;
});
afterAll(() => app.close());
it('answers 408 after the timeout', async () => {
const res = await fetch(`http://127.0.0.1:${port}/slow`);
expect(res.status).toBe(408);
});
it('aborts when the client disconnects', async () => {
const req = http.request({ port, path: '/slow' });
req.on('error', () => undefined);
req.end();
setTimeout(() => req.destroy(), 50);
// assert on what the handler saw, e.g. a flag it sets after its await
});

Testing a disconnect needs a raw http.request you can destroy(); supertest waits for a response. The library’s own e2e suite does exactly this on Express and Fastify.