On Monday, October 6, 2014 1:53:51 PM UTC-7, David Karr wrote: > > 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. >
I did notice that the main Protractor page has the following statements: * Protractor supports Angular-specific locator strategies * You no longer need to add waits and sleeps to your test Is this the essential value proposition for Protractor over plain Selenium WebDriver? -- 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 angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
