t.assert is not a function

[Quramy]

Version

v22.3.0

Platform

Darwin CF0393.local 21.6.0 Darwin Kernel Version 21.6.0: Thu Sep 29 20:13:56 PDT 2022; root:xnu-8020.240.7~1/RELEASE_ARM64_T6000 arm64

Subsystem

test_runner

What steps will reproduce the bug?

/* assert.js */

import assert from "node:assert";
import { test } from "node:test";

test("context assert", (t) => {
  t.assert(true);
});

test("assert module", (t) => {
  assert(true);
});

node --test assert.js

✖ context assert (0.720083ms)
  TypeError [Error]: t.assert is not a function
      at TestContext.<anonymous>
      at Test.runInAsyncScope (node:async_hooks:206:9)
      at Test.run (node:internal/test_runner/test:856:25)
      at Test.processPendingSubtests (node:internal/test_runner/test:565:18)
      at node:internal/test_runner/harness:248:12
      at node:internal/process/task_queues:140:7
      at AsyncResource.runInAsyncScope (node:async_hooks:206:9)
      at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

t.assert can be called as a function.

What do you see instead?

✖ context assert (0.720083ms)
  TypeError [Error]: t.assert is not a function

Additional information

I read about context.assert of Test runner:

https://nodejs.org/docs/latest/api/test.html#contextassert

And this doc says the following:

The top-level functions from the node:assert module are exposed here

Is this difference intended ? (I feel it lacked consistency)

[climba03003]

I believe it means the functions inside assert is exposed instead of mirroring the whole assert.

[Quramy]

If you are not intentionally exposing t.assert(), you may close this issue.

[RedYetiDev]

An object containing assertion methods bound to context. The top-level functions from the node:assert module are exposed here for the purpose of creating test plans.

t.assert isn't a function, but an object, try logging it in the console to see what it can do

(As previously stated by @climba03003)

[cjihrig]

I can confirm that it was not my plan for the t.assert object to be the assert() function. Whether that is something we want to support or not - I don't have an opinion either way, as long as it is implemented in a way that the t.assert function could be changed in the future programmatically. I would still like to add an API for decoupling t.assert from the assert module (snapshot tests were the proof of concept for that).

[Quramy]

@cjihrig

I can confirm that it was not my plan for the t.assert object to be the assert() function.

Thanks for your answer !