Unit testing of nodejs client

One alternative that I have just come up with would be something like the following example where we would get ourselves a router object, pass it to the routes function and then work with that directly without any server.

import { createConnectRouter } from '@bufbuild/connect';
import { ConfigService } from '../../gen/service_connect';
import getRoutes from './ConfigService.js';

const router = createConnectRouter();
getRoutes()(router);

describe('ConfigService', () => {
    test('getServers', () => {
        // …somehow work with "router.handlers"
    });
});

@kubijo I chose the same way to generate routes and mock service, still some issues blocked me. Like how to use connect-web to request data when testing, it actually depends on Fetch. Any insights on that?

I have not moved forward in any meaningful way with this yet, and I'm still keeping it in the backlog...

I did, however, rewrite the service implementation to a class that implements the ServiceImpl type for a nicer code structure around handlers.

Furthermore, I suppose this should make the testing easier too by not involving even the router.
I think this should allow me to just instantiate the class and test the route handlers with message objects... It certainly works for the router in runtime as it doesn't mind the nature of object that it gets as long as it finds expected handlers.

OK, so I've revisited this and validated the pattern.

Service.ts

You still get type hinting this way & don't have to declare all of your handlers in the route handler.

export default class Service implements ServiceImpl<typeof YourService> {
    async listConfigFiles() { … }
}

Service.spec.ts

import Service from './Service';
const s = new Service();

describe('Service', () => {
    test('listConfigFiles', async () => {
        const response = await s.listConfigFiles();
        expect(response).toEqual(…);
    });
});