BOLLB
Deno•15mo ago•
6 replies
BOLL

Possible to use Deno.test for callbacks?

I've been implementing tests to make sure the porting of my main project to Deno is working out as expected, coupled with this is a WebSocket server done with Deno.serve. For this the test needs to handle both a server and client session, waiting for callbacks to come through.

Right now my test finishes prematurely even if I await the termination of the server, I need to set both sanitizeOps: false and sanitizeResources: false to have the test finish at all, but then it skips any assert defined in the callbacks.

My previous experience is with Mocha where we get the done callback to run to finish the current test, but for Deno.test I only see us getting the option to make the test caller asynchronous, which in this case doesn't seem to help me.

Basically, is it possible to have something like this working:
Deno.test('ws session', async ()=>{
  const srv = new Server()
  srv.onOpen = ()=>{ /* send message to client */ }
  srv.onMessage = ()=>{ /* confirm then disconnect client */ }
  srv.onClose = ()=>{ /* finish test */ }
  const cli = new Client()
  cli.onMessage(()=>{ /* respond to server */ })
})

My problem now is as mentioned that the callbacks will happen at arbitrary points in time and aren't made to be awaited, so they won't be blocking the test from finishing.

I can see adding a few more options to the test options object, like awaitDone and timeout, to enable running until manually marked as done or failing when timing out. To finish a test Deno.TestContext could have a .done() method on it. Unless this already exists, but I haven't found how to achieve this in the docs or in the types, yet.

The simulated example but with the above suggestion:
Deno.test('ws session', {awaitDone: true, timeout: 5000}, async (t)=>{
  const srv = new Server()
  // ...
  srv.onClose = ()=>{ t.done() }
  // ...
})
Was this page helpful?