Fix running bun test on multiple node:test tests

[190n]

What does this PR do?

Fixes #19200

How did you verify your code works?

Added to node-test.test.ts

[robobun]

^{Updated 11:21 AM PT - Jul 23rd, 2025}

@190n, your commit 58de5d3 is building: #21284

[jordanebelanger]

@190n If this can help you potentially debug, I can still make the tests be skipped under certain circumstances, take this snippet for example:

import { test, after } from 'node:test'
import { strict as assert } from 'node:assert'
import { build } from '../helper'

import type { FastifyInstance } from 'fastify'

after(async () => {
  // Cleanup logic if needed
})

test('resource routes', async () => {
  const app: FastifyInstance = await build()

  await test('should create and update a resource', async () => {
    throw new Error('this should fail the test')
  })
})

When this is ran, the inner test does not get executed (doesn't show up in the console list nor is the thrown error catched/visible)

[190n]

It looks like we don't intend to support that yet:

bun/src/js/node/test.ts

Lines 146 to 148 in 3278969

	if (this.#insideTest) {
	throwNotImplemented("test() inside another test()", 5090, "Use `bun:test` in the interim.");
	}

I think this will be an effort for a different PR. However, I will see if I can figure out why the error isn't being thrown, since that could probably be confusing.

[190n]

@jordanebelanger thanks for bringing this up, the issue was we would only throw the error if you used the context, e.g. using t.test in test("outer", t => t.test("inner", ...)). I've fixed this and added a test that we emit the error here.

We'll add support for nested tests someday but that's outside the scope of this PR. I think providing an error in this case is still a worthwhile improvement over status quo.

[dylan-conway]

Two comments, looks good afterwards