Version
v20.12.0
Platform
Linux vali 6.8.0-76060800daily20240311-generic #202403110203171019808822.04~1a3dbc7 SMP PREEMPT_DYNAMIC Mon M x86_64 x86_64 x86_64 GNU/Linux
Subsystem
assert
What steps will reproduce the bug?
Create an empty directory with the following file named test.mjs:
import assert from 'node:assert/strict'
import { test } from 'node:test'
test('fruit', () => {
assert.equal('apple', 'pear')
})Now run the following:
node test.mjs
node --test
How often does it reproduce? Is there a required condition?
In my experience always.
What is the expected behavior? Why is that the expected behavior?
I expected the assertion error to always be colorful, at least if the rest of the test output is.
What do you see instead?
The assertion error is colorful when running a test script directly, but not when it’s run via node --test.
Additional information
Potentially related environment variables from my desktop session:
COLORTERM=truecolor
DESKTOP_SESSION=pop
GDMSESSION=pop
SHELL=/bin/zsh
SHLVL=1
TERM=xterm-256color
From a Docker container:
Version
v20.12.0
Platform
Linux vali 6.8.0-76060800daily20240311-generic #202403110203
171019808822.04~1a3dbc7 SMP PREEMPT_DYNAMIC Mon M x86_64 x86_64 x86_64 GNU/LinuxSubsystem
assert
What steps will reproduce the bug?
Create an empty directory with the following file named
test.mjs:Now run the following:
How often does it reproduce? Is there a required condition?
In my experience always.
What is the expected behavior? Why is that the expected behavior?
I expected the assertion error to always be colorful, at least if the rest of the test output is.
What do you see instead?
The assertion error is colorful when running a test script directly, but not when it’s run via
node --test.Additional information
Potentially related environment variables from my desktop session:
From a Docker container: