You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Darwin MacBook-Pro.local 22.5.0 Darwin Kernel Version 22.5.0
Subsystem
No response
What steps will reproduce the bug?
pnpm init to initialize a project
create test directory and a index.js file inside it,
import test from 'node:test';
import assert from 'node:assert'
test.only('synchronous passing test', (t) => {
// This test passes because it does not throw an exception.
assert.strictEqual(1, 1);
});
test('synchronous failing test', (t) => {
// This test fails because it throws an exception.
assert.strictEqual(1, 2);
});
test('asynchronous passing test', async (t) => {
// This test passes because the Promise returned by the async
// function is not rejected.
assert.strictEqual(1, 1);
});
Run node --test-only
How often does it reproduce? Is there a required condition?
There are no required conditions. Anytime, I execute the tests using node --test-only it opens REPL.
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
I see the node REPL, instead of test execution.
❯ node --test-only
Welcome to Node.js v20.4.0.
Type ".help" for more information.
>
Additional information
No response
The text was updated successfully, but these errors were encountered:
Version
v20.4.0
Platform
Darwin MacBook-Pro.local 22.5.0 Darwin Kernel Version 22.5.0
Subsystem
No response
What steps will reproduce the bug?
pnpm init
to initialize a projecttest
directory and aindex.js
file inside it,node --test-only
How often does it reproduce? Is there a required condition?
There are no required conditions. Anytime, I execute the tests using
node --test-only
it opens REPL.What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
I see the node REPL, instead of test execution.
Additional information
No response
The text was updated successfully, but these errors were encountered: