We're moving #Angular to #Jest and #WebTestRunner.

We've seen a lot of movement in the web testing ecosystem towards Jest and want to make it more available for #AngularCLI users.

We've also been particular impressed with Web Test Runner and are looking forward to bringing it into the Angular ecosystem as well.

Check out the #AngularBlog for all the details:

https://medium.com/angular-blog/moving-angular-cli-to-jest-and-web-test-runner-ef85ef69ceca

@web/test-runner and StoryBook are great tools to work with in front-end. Till now the another handy tool was not available in this stack - MSW mocking.

It took a bit of trickery to baptize MSW into es6 modules. If you want to use MSW for #webcomponents testing, take a look

#modernweb #webtestrunner #msw

https://blog.firsov.net/2023/03/how-to-integrate-msw-queries-mocking.html

So I've been doing a bit of research into #web #UnitTesting #tooling (#Jest, #Vitest, #Jasmine, #Karma, #WebTestRunner, ...).

I'm curious if there's any interest in a blog post on some of my takeaways about aspects like:

* Test runners vs test frameworks.
* Browser-based runners vs Node-based runners.
* Changes in the ecosystem.
* Future directions of JS unit testing.
* ...

@eliajf I was mostly looking into test runners moreso than test frameworks.

#Jest is still dominant by a huge amount, but #WebTestRunner and #JasmineBrowserRunner looked interesting to me. I've had good experiences with WTR in the past, but haven't tried Jasmine's browser runner.

https://modern-web.dev/docs/test-runner/overview/
https://www.npmjs.com/package/jasmine-browser-runner