Skip to main content
Explained why I would choose Protractor for AngularJS
Source Link
Charlie
  • 193
  • 8

If it is an Angular application I would go for Protractor

EDIT:

Protractor was made for Angular Apps. You don't have deal with elements not being visible yet due to page loads. Protractors deals with it for you

As far as I know CodedUI des not provide this functionality. Correct me if I'm wrong.

Resource reason: Most Angular projects are javascript intensive. Which means your devs will be able to maintain the protractor tests too. Might come in handy later.

If it is an Angular application I would go for Protractor

If it is an Angular application I would go for Protractor

EDIT:

Protractor was made for Angular Apps. You don't have deal with elements not being visible yet due to page loads. Protractors deals with it for you

As far as I know CodedUI des not provide this functionality. Correct me if I'm wrong.

Resource reason: Most Angular projects are javascript intensive. Which means your devs will be able to maintain the protractor tests too. Might come in handy later.

Source Link
Charlie
  • 193
  • 8

If it is an Angular application I would go for Protractor