Guess I'll look at something other than @jestjs_ if they can't get thier naming / getting started right.

Ever wondered why many @jestjs_ setups use "--maxWorkers=50%"?

Jest 30 has just shipped. It's faster, uses less memory and brings new testing APIs.

#This_is_LiveCodes Unit tests, running in the browser using @jestjs_ 🃏 Dark theme Custom theme color link 👇

Just crafted my first testing code for an Express API using @jestjs_ 🚀 #Jest #Testing

Hey Software Devs, I am building something called #mocklets for speedy testing with @jestjs_ To explain what it is i have 4 images below. What if you could do all these (in each image) instead of manually doing them like you currently do when testing with #jestjs_ ? 👇🏾👇🏾👇🏾

If you want to know the difference in testing @reactjs with @jestjs_ between fake timers enabled globally with enableGlobally flag and using fake timers per test then check this out https://t.co/RUb6eJf4lb TLDR; Just don't use enableGlobally during your react tests ;)

EarlyAI makes achieving 100% coverage with @jestjs_ easy🌟 Our VSCode extension enhances test coverage tracking by: ✅ Real-time coverage display ✅ Automatic updates after test generation ✅ Instant identification of under tested areas Check the links in the comments ⬇️

When @jestjs_ will make a new release ? the last release was 2023

Hey Everyone, What is the preferred #JavaScript Testing Framework? @jestjs_ #Mocha @Cypress_io

I made my own test-runner because tools like @vitest_dev and @jestjs_ didn't quite fit my use-case. It's both pretty simple and very difficult if you're not using a build system. Because Async Context is not a thing in JS yet (stage 2 @TC39), I used hacky Error stacks.

For @vitest_dev and @jestjs_ maintainers, i think it's high time to improve on the APIs associated with `expect(..)`. There's room for improvement. We might need to stop using this API design (It's limiting...): `expect(..).toHaveBeenCalledWith(..)` And try this one: 👇🏾👇🏾

🤯 @vitest_dev >>>>>>>>>>>>> @jestjs_ i just spent hours trying to configure jest with ESM to no avail. eventually quit and tried vitest upon a stackoverflow suggestion. worked out the box. what a gem. https://t.co/FifJopVm3w

Can anyone in the react space help me with this? CRA with React @TestingLib and @jestjs_ . PS: I am doing cleanup

What's next for nut.js? One thing to expect from our next release is improved support for native application testing on Windows. It'll bring testing tools from the web to the desktop, allowing you to write tests for your application using either @jestjs_ or @vitest_dev! 🎉

Anyone else run into @vitest_dev and @jestjs_ types conflicting in @WebStormIDE and Webstorm not knowing that vitest types exist? (The tests run fine). Sometimes it will suggest it in quick fix but does't know the globals exist. (tsconfig spec file is setup correctly). Ideas?

Having users keep a list of ESM-only dependencies to ignore "transform" on is the, as advertised, delightful Jest experience? As a maintainer of ESM-only modules I am not delighted being the support channel for @jestjs_ users who struggle to use web-compatible ESM modules.

Day: 58/100 - Create some tests and also all the tests @jestjs_ - Authentication, Admin routes test and some user routes - Also work on my ChatDapt clone project in the project to add the database and create auth routes - Continue these days #Coding #LearnInPublic #buildinpublic

Think I just reached a very good testing flow with superagent, @jestjs_ , @Docker , @prisma , @UseExpressJS , @Redisinc all with auth. Everything is abstracted into function. Will share more by tonight. #buildingpublic