spectator VS Angular

Is the Angular team aware of NG Mocks and NG Spectator?

I tried a couple of courses several years ago but honestly didn't find them very helpful. (That was several years ago, so things may have changed since then.) What I did find immensely helpful was installing @ngneat/spectator and reading over its documentation. Its APIs are so much simpler and more ergonomic that it didn't take long to memorize the workflow and get to be productive with it.

Does anyone use spectator(https://github.com/ngneat/spectator) as a tool for unit tests with Angular

ngneat.github.io

Follow https://testing-angular.com/. I use https://github.com/ngneat/spectator instead of Angular weird test boilerplate

If your looking for a way to make testing simpler check out https://github.com/ngneat/spectator

I've had huge success using spectator https://github.com/ngneat/spectator

Another possibility is to look into Spectator https://github.com/ngneat/spectator. In Spectator, you can add mocks with a simple array. I have a blog series on it here https://medium.com/ngconf/introduction-to-spectator-4d03edf514dd. The next part talking about how to mock observables should be published soon.

I have been reading the spectator code quite a bit. "GitHub - ngneat/spectator: 🦊 🚀 A Powerful Tool to Simplify Your Angular Tests" https://github.com/ngneat/spectator

/** * https://github.com/angular/angular/blob/75a186e321cb417685b2f13e9961906fc0aed36c/packages/core/src/render3/reactivity/untracked.ts#L15 * * packages/core/src/render3/reactivity/untracked.ts * **/ export function untracked(nonReactiveReadsFn: () => T): T { const prevConsumer = setActiveConsumer(null); try { return nonReactiveReadsFn(); } finally { setActiveConsumer(prevConsumer); } }

source: https://github.com/angular/angular/issues/46542

Besides the dangers, mentioned by Angular docs (infinite loops, change detection errors), there is another thing, that might be quite nasty: effects are executed in a reactive context, and any code you call in effect, will be executed in a reactive context. If that code reads some signals, they will be added as dependencies to your effect. Here Alex Rickabaugh explains the details.

In June 2023, the Angular team raised a new RFC to implement control flow syntaxes within Angular. They gave the following rationale for introducing control flow syntax:

For scheduling, I use awesome code I found in the Angular source code.

Just to give you more context, I led the migration of several AngularJS applications to the newer Angular Framework. My client finally decided to make that move following the AngularJS deprecation announcement (stay up to date please 🙏)️.

Link — angular/CONTRIBUTING.md

Angular v17 was released some months ago with a ton of new features, a brand new logo and the new blog angular.dev.