ts-mockito VS ng-mocks

If you are using a mocking library, such as sinon, jest-mock, or ts-mockito, make sure that it is compatible with Jest. You may need to install additional packages or configure them in your configuration file. For example, to use sinon with Jest, you can install the sinon-jest package and add the following to your configuration file:

I discovered that exists ts-mockito ( https://github.com/NagRock/ts-mockito) a Mocking library for TypeScript, and I'm thinking about introducing this to our enterprise project

There's a very cool library called ts-mockito, it works very well when you use dependency injection in your code (as we're doing now). It allows you to create mocks, stub function calls, and many other cool features, definitely check it out! I'm going to use it to test our AuthRepository.

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

No neither of those. You're unit testing the component, so you don't want any external interference. You can create a mock version of the service, I like using ng-mocks to simplify a lot of this: https://www.npmjs.com/package/ng-mocks

No way, you just mock the services. Check out this library: https://www.npmjs.com/package/ng-mocks

I recommend using MockModule from ng-mocks https://www.npmjs.com/package/ng-mocks

8. NG-Mocks

You can have a look at ng-mocks. It provides a great toolset for angular mocks.

Also, for mocking, I recommend looking into ng-mocks. https://github.com/ike18t/ng-mocks It makes mocking really easy.

Correct. When unit testing, you want to test the unit (parent component) in isolation. To do this, you can use something like ng-mocks (my personal favorite) to create mock components. You could also use the NO_ERRORS_SCHEMA but I don't recommend this because I like to verify that my component loads w/ all of its dependencies (even if the are just mocks). If you test your parent component w/ all of its child components, then you are doing a form of integration testing. I tend to refer to it as a grey area between unit and integration testing because there are valuable tests that can be written fairly easily and cheaply that don't truly isolate parent components from their child components.