[Node Test Runner] getting 'Promise resolution is still pending but the event loop has already resolved'

[AaronNGray]

I am getting 'Promise resolution is still pending but the event loop has already resolved' when using Node Test Runner.

I am looking at a test migration of a repo to the Node Test Runner :- https://github.com/AaronNGray/grant/tree/node-test-runner

I am getting the error lots and lots of times :-

▶ oauth2
  ▶ success
    ✖ google
      'Promise resolution is still pending but the event loop has already resolved'

  ✖ success

    'Promise resolution is still pending but the event loop has already resolved'

  ▶ subdomain
    ✖ auth0
      'Promise resolution is still pending but the event loop has already resolved'

  ✖ subdomain

    'Promise resolution is still pending but the event loop has already resolved'

A full log is here :-
test.txt

Is there a simple fix for this please ?

This is obviously a candidate case for a Node Test Runner migration HOWTO guide !

[cjihrig]

I haven't tried to debug your entire test suite, but here are a couple things to note:

• The error you're seeing means that the process was ready to exit but there were still tests pending. So, it looks like there are no ref'ed handles or requests keeping the event loop alive.
• I noticed a number of EADDRINUSE errors in your logs. I'm assuming the event loop isn't being kept alive because of this.

node --test test/handler/oidc.js fails with your current setup. I updated the code to use port 6000 instead of 5000 and then the test file passed for me. I'm guessing that is the cause (or at least one cause) of your problems.

[AaronNGray]

Thank you for looking at this. So you think it might possibly be in part a knock on effect. I noticed that Node Test Runner uses asyncronous describes and its so it must be coded differently from Mocha. I am wondering how I go about this and if it can be typified into a number of patterns ?

node --test test/handler/oidc.js works when invoked on its own.