feat(learn): add section for dynamically generating test cases

[JakobJingleheimer]

Description

Validation

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Jan 5, 2025 3:32pm

[AugustinMauroy]

I'm not fan of the provided example because it's based on experimental api.

maybe do same things as this test (do with jest). But I mean based on hand written variable
https://github.com/nodejs/nodejs.org/blob/main/apps/site/util/__tests__/detectOS.test.mjs

[JakobJingleheimer]

Hmm, I think that example isn't quite as good. The one I have is unknowable.

I'm happy to just switch the assertion (and far less work 😅)

EDIT: ohhh! Wait, is the experimental API you're concerned about globSync? (Rather than assert.partialDeepStrictEqual)

[JakobJingleheimer]

Suggested change

	assert.partialDeepStrictEqual(pjson.keywords, [
	'node.js',
	'sliced bread',
	]);
	assert.match(pjson.name, /@nodejs\/[a-z \-]+/);