I really enjoyed this video because you took a problem, demonstrated why it happens, demonstrated a solutions with explanation - then provided information on a third party product. With this video I learned so much, even beyond testing

@RainerHahnekamp

4 ай бұрын

Thanks a lot Dylan!

Great tutorial! Was able to finally understand how to inject mocks for standalone stuff. Thanks 😁

@RainerHahnekamp

4 ай бұрын

Great to hear, you're welcome

Amazing content as always!!!!!

@RainerHahnekamp

2 ай бұрын

Thanks Dany and best wishes!

Awesome, great explanation. This is what I was looking for

@RainerHahnekamp

4 ай бұрын

👍

This is great content as always. The concern I have about moving to standalone components is the bundle size. I haven't taken a deep look into this, but I've read here and there that there's a lot of code duplicated and your app actually grows in size. I'm sure it can be mitigated with lazy loading, but it's something to consider.

@RainerHahnekamp

Ай бұрын

Hi, where did you hear about the bundle size issue? Could it be that you are mistake standalone with the barrel files? Having a lot of barrel files (index.ts) will problems to your bundler because it might not be able to tree-shake them efficientyl, and you may end up with a huge initial bundle. Regarding Standalone vs NgModule, there is no impact on the bundle size.

Indepth Info as always, thanks Rainer

@RainerHahnekamp

4 ай бұрын

Thanks as well Vinit.

Thanks Rainer, awesome video !

@RainerHahnekamp

4 ай бұрын

You are very welcome Rudy

Very good thanks...

@RainerHahnekamp

4 ай бұрын

Thanks Roland.

Thanks for video)

@RainerHahnekamp

4 ай бұрын

You're very welcome!

another great explanation! thank you! it's embarassing but in my company we got new schematics using overrideCopmonents and I just did not bother finding out why... sometimes the test did not work and then I spend hours trying out different things. So happy I now understand, what it does!

@RainerHahnekamp

4 ай бұрын

Yeah, so TestBed.override... is something we don't see that often but it is quite powerful

I just ran into a situation like this today but with component store in a child component being the troublesome thing. I think this solution will work a lot better than what I tried to do. Thanks.

@RainerHahnekamp

4 ай бұрын

You're welcome Michael! Happy to help.

Cool!!!

@RainerHahnekamp

4 ай бұрын

Thanks Paul!

How about non-standalone dependencies? I have in my imports array some modules with related dependencies. I want to replace them with stubs which I already have. Should I create test module and include all stubs components in it and add it to the standalone imports?

@RainerHahnekamp

4 ай бұрын

So you will always have to configure the TestingModule. There is no other way if you want to test via the DOM (and it is also the official recommendation). Without standalone, mocking is easier. you just declare your stubs instead the original ones. Declare, not import.

You mention the usage of ng-mocks library to Mock Standalone Components. We use this as wel to mock our services that we provide. However, sometimes, it uses the actual service instead of the mocked one. How do you properly mock these services that you provide?

@RainerHahnekamp

3 ай бұрын

Hi, could it be the case that those services are provided by the component? Otherwise, it has to work as expected. Can you maybe provide an example?

@NicolasMaas

3 ай бұрын

@@RainerHahnekamp The services are indeed all provided on the component itself.

how to test Angular Guards ?

@RainerHahnekamp

4 ай бұрын

Do you want to test only the guards or the guard in combination with a Component? In the first case, check out this video kzread.info/dash/bejne/n4Gdtc-MpNqtf7g.html, in the second that one: kzread.info/dash/bejne/dqeD2rlyhK7Yn9I.html

@besara_

4 ай бұрын

@@RainerHahnekamp really, appreciated 👏