Regarding Angular 5 Automation using Protractor with C#

[ArunSrid]

This is with regards to Angular 5 Automation with Protractor using c#

My application is developed based on Angular5 with Primeng UI components and kendo grid. In order to Automate have few queries as mentioned below:

a) Can protractor be used to Automate angular 5 application ? b) When I try to inspect, there are no ng-model, ng-reflect, ng-binding, ng-repeat etc.. available ? Should I discuss with development team to add these locators for Angular 5 or any other locators are available ? c) can I use the nuget package protractor in visual studio and start writing code in c#.Does that protractor nuget package support angular 5 Automation ? In our company I am not supposed to use JavaScript or typescript. How feasible it is to write in c# using the protractor package ? d) Do you have any guideline that a developer should follow in Angular 5 development to cater E2e testing using protractor.net. Like ex for a input box what angular attribute to be added ? For a drop down ? For a grid what angular attribute to be added ? e) There are two types of build prod build and dev build. Actually we are supposed to test in prod build but unable to find any angular components in prod build, as the webpack tool coverts all the angular components to javascript . In this case where there are no angular components in prod build. How to Automate ?

Please help me with these queries and in case you have any solution for protractor.net please share.

[JacobMillward]

From my experience, it can be used for angular2+ apps, with caveats:

• I've not managed to get any of the angular locators to work, I've fallen back on id's and classnames
• The synchronization doesn't always seem to work, and I have a few pages where it just times out; I can't figure out the underlying cause. Setting ngDriver.IgnoreSynchronization = true; and doing my own waiting works.

[disophisis]

To add to @JacobMillward , we recently switched back to typescript and the protractor library available on NPM. That library seems to have its own problems with synchronization as well. Lots of timing out, lots of failing to wait for routing even where HTTP requests are being made. I'm not sure if even the 1st party protractor library is that well supported anymore, based on those experiences.