Protractor VS ng-mocks

Cypress is a next-generation front-end Automation testing tool built for modern web applications. It is a JavaScript-based end-to-end testing framework and is known for faster test execution as compared with other testing tools (like Selenium or Protractor).

Protractor repo (link)

Protractor has been deprecated for a while on the Angular CLI side and given Nx has had Cypress support for a while it has never been a popular choice. Starting with this release we're deprecating the generator for setting up Protractor and we're planning on removing support entirely in Nx v15.

In recent releases, the Angular CLI kept reducing its feature set, mainly due to tools such as Protractor as well as TSLint being deprecated. As a result, starting with Angular 14, the Angular CLI provides the following when generating a new application:

The Protractor testing framework was created for e2e testing of Angular apps. https://www.protractortest.org/

Future of Angular E2E & Plans for Protractor · Issue #5502 · angular/protractor

In April, the Angular team has announced plans to end the support of Protractor at the end of 2022.

"The Angular team plans to end development of Protractor at the end of 2022 (in conjunction with Angular v15)." - https://github.com/angular/protractor/issues/5502

Angular will deprecate Protractor soon https://github.com/angular/protractor/issues/5502

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.