feat(jest-to-node-test-runner): add initial implementation by Ceres6 · Pull Request #70 · nodejs/userland-migrations

Ceres6 · 2025-05-11T16:40:32Z

No description provided.

Ceres6 · 2025-05-11T16:42:15Z

I have just started working on this. Any feedback is appreciated.

recipes/jest-to-node-test-runner/src/workflow.test.ts

AugustinMauroy · 2025-05-12T06:45:51Z

recipes/jest-to-node-test-runner/src/workflow.test.ts

+		const importStatement =
+			'import { describe, it } from "node:test";\nimport { expect } from "expect";\n';
+
+		t.assert.deepStrictEqual(result, `${importStatement}${source.split("\n").slice(1).join("\n")}`);


we can use snapshot https://nodejs.org/docs/v22.15.0/api/test.html#snapshot-testing

Yeah, I will use that in the end, but since I'm changing this a lot I didn't want to have to update them all the time yet

hint node --run test -- --test-update-snapshot 😁

recipes/jest-to-node-test-runner/tsconfig.json

AugustinMauroy · 2025-05-12T06:50:40Z

You should add on your todo for this codemod:

way to remove jest dep, then verify if expect is downloaded
that need to have something that check which package manager is used
check if un-imporded jest describe, it is supported by the codemod
found a way to modify scripts key in package.json to use node --test

recipes/jest-to-node-test-runner/test/spawn-promisified.ts

Ceres6 · 2025-05-14T13:54:21Z

You should add on your todo for this codemod:

way to remove jest dep, then verify if expect is downloaded
that need to have something that check which package manager is used

check if un-imporded jest describe, it is supported by the codemod

found a way to modify scripts key in package.json to use node --test

Agreed. the un-imported one already works, maybe I should add a different test for that

avivkeller · 2025-05-14T17:57:01Z

recipes/jest-to-node-test-runner/.codemodrc.json

+{
+  "$schema": "https://codemod-utils.s3.us-west-1.amazonaws.com/configuration_schema.json",
+  "name": "jest-to-node-test-runner",
+  "description": "Convert Jest tests to Node Test Runner tests",


Maybe call this "node:test" instead of "Node Test Runner"

And "jest-to-node-test", etc

avivkeller · 2025-05-14T17:57:52Z

recipes/jest-to-node-test-runner/README.md

+
+This package transforms Jest test files into Node Test Runner test files.
+
+This is a one-and-done process, and the updated source-code should be committed to your version control (eg git); thereafter, source-code import statements should be authored compliant with the ECMAScript (JavaScript) standard.


Is it a guaranteed "one-and-done"? I don't think we should make any promises.

At least right now, this definitely is not a one and done scenario

"One-and-done" refers to it being a discrete, one-off process (contrary to a loader that runs every time).

recipes/jest-to-node-test-runner/package.json

recipes/jest-to-node-test-runner/src/workflow.test.ts

avivkeller · 2025-05-14T18:02:36Z

recipes/jest-to-node-test-runner/src/workflow.ts

+		"describe",
+		"it",
+		"test",
+		"beforeEach",
+		"afterEach",
+		"beforeAll",
+		"afterAll",


What if the user defined and/or imported these from elsewhere?

It's still WIP, I'm trying to cover low hanging fruits first so I can test it with simple projects and then I/we could support projects with less standard usage

Ceres6 · 2025-05-28T16:20:34Z

I added a bunch of features, started a TODO list and left some TODO/FIXME were I think things could be done better. As before any feedback is welcomed.

I know it needs to be split across functions/files but I was delaying that until some abstractions become obvious.

What I'm planning next is:

support timers config options
support .each, .concurrent and failing
support timeout arg in suites/tests
improve module mocking support

I want something like

jest.mock('../myModule', () => {
  // Require the original module to not be mocked...
  const originalModule = jest.requireActual('../myModule');

  return {
    __esModule: true, // Use it when dealing with esModules
    ...originalModule,
    getRandom: jest.fn(() => 10),
  };
});

to work and hopefully support most of the https://jestjs.io/docs/jest-object#mock-modules methods

AugustinMauroy · 2025-05-28T16:38:14Z

recipes/jest-to-node-test/src/workflow.test.ts

+
+		t.assert.snapshot(result);
+	});
+


Suggested change

it("should be a runnable test", async () => {

/**

* 1. run the codemod

* 2. up a child process

* 3. assert output code + stdout & stderr

*/

});

AugustinMauroy · 2025-05-28T16:39:31Z

recipes/jest-to-node-test/src/workflow.test.ts

in some case you use ts.assert.something
you have to import assert module to do some asserting and only if you need to do some snapshots use t.assert.snapshot

AugustinMauroy · 2025-06-24T13:04:45Z

to modify dep read that https://docs.codemod.com/building-codemods/package-requirements#param-deps

AugustinMauroy · 2025-08-02T20:00:05Z

Hey on we are going to use new codemod CLI/approach

https://codemod.com/blog/new-codemod-cli
https://docs.codemod.com/cli/cli-reference

…est-runner

AugustinMauroy · 2025-12-13T09:55:32Z

Bump @Ceres6 👋

…est-runner

AugustinMauroy · 2025-12-13T16:36:09Z

recipes/jest-to-node-test/package.json

+  "type": "module",
+  "main": "./src/workflow.ts",
+  "scripts": {
+    "test": "npx codemod@next jssg test -l typescript ./src/workflow.ts ./"


Suggested change

"test": "npx codemod@next jssg test -l typescript ./src/workflow.ts ./"

"test": "npx codemod jssg test -l typescript ./src/workflow.ts ./"

BTW no nedeed anymore

AugustinMauroy reviewed May 12, 2025

View reviewed changes

recipes/jest-to-node-test-runner/src/workflow.test.ts Outdated Show resolved Hide resolved

AugustinMauroy reviewed May 12, 2025

View reviewed changes

recipes/jest-to-node-test-runner/tsconfig.json Show resolved Hide resolved

JakobJingleheimer reviewed May 12, 2025

View reviewed changes

recipes/jest-to-node-test-runner/test/spawn-promisified.ts Show resolved Hide resolved

avivkeller reviewed May 14, 2025

View reviewed changes

Ceres6 force-pushed the feat/jest-to-node-test-runner branch 4 times, most recently from b409260 to 6d32aed Compare May 28, 2025 16:10

feat(jest-to-node-test): add initial implementation

b7ad997

Ceres6 force-pushed the feat/jest-to-node-test-runner branch from 6d32aed to b7ad997 Compare May 28, 2025 16:22

AugustinMauroy reviewed May 28, 2025

View reviewed changes

AugustinMauroy moved this to 🏗 In progress in Userland Migrations Board Jul 25, 2025

AugustinMauroy added this to Userland Migrations Board Jul 25, 2025

Ceres6 added 2 commits August 10, 2025 13:47

Merge remote-tracking branch 'upstream/main' into feat/jest-to-node-t…

64539db

…est-runner

Merge remote-tracking branch 'upstream/main' into feat/jest-to-node-t…

8eb4e67

…est-runner

Ceres6 added 3 commits December 13, 2025 12:26

feat: migrate to new CLI

20befd7

fixup! feat: migrate to new CLI

97e697e

Merge remote-tracking branch 'upstream/main' into feat/jest-to-node-t…

a1e0289

…est-runner

AugustinMauroy reviewed Dec 13, 2025

View reviewed changes


		This package transforms Jest test files into Node Test Runner test files.

		This is a one-and-done process, and the updated source-code should be committed to your version control (eg git); thereafter, source-code import statements should be authored compliant with the ECMAScript (JavaScript) standard.

+it("should be a runnable test", async () => {
+  /**
+  * 1. run the codemod
+  * 2. up a child process
+  * 3. assert output code + stdout & stderr
+  */
+});

	"test": "npx codemod@next jssg test -l typescript ./src/workflow.ts ./"
	"test": "npx codemod jssg test -l typescript ./src/workflow.ts ./"

Uh oh!

Conversation

Ceres6 commented May 11, 2025

Uh oh!

Ceres6 commented May 11, 2025

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

AugustinMauroy commented May 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Ceres6 commented May 14, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Ceres6 commented May 28, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AugustinMauroy commented Jun 24, 2025

Uh oh!

AugustinMauroy commented Aug 2, 2025

Uh oh!

AugustinMauroy commented Dec 13, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

AugustinMauroy commented May 12, 2025 •

edited

Loading