I'm having trouble finding anything that clearly states from a high level, 
why someone should use Protractor for writing e2e tests for AngularJS 
applications, as opposed to just using Selenium WebDriver to connect to a 
deployed instance of the app.  I imagine a statement to this effect is 
implicitly buried in multiple places in the Protractor documentation, but 
I'm really looking for a high-level statement that addresses this.

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to