alphagit / a-pattern-restrict Goto Github PK

After Selenium 3.0, the server changed the interaction APIs and the shutdown method is no longer accepted by the server. This means that our current test suite cannot shut down the server after running the tests.

Change the interaction from the Selenium server (currently using grunt-protractor-webdriver) to a new version that can setup the selenium standalone server and shut it down later on.

Changing the browser capability (browserName) to internet explorer has Selenium complaining that the IE driver is not present.

Create steps to configure (or setup an automated way to configure it) so that tests can be run locally for IE.

The automated tests currently blow up in SauceLabs -- the messages indicate that Protractor is not able to find Angular in the test pages. In the community, this is regarded as a problem with in-site navigation (or are those about an old version of protractor?)

Notice that the in-site navigation is required so that we can have multiple components being tested at the same time without interfering with each other.

If that was not possible, maybe an alternative would be to completely get rid of navigation in the test suite and have all components stacked one along another. They should be independent. Just make sure that the elements do not render the same IDs.

The documentation in this version of the directive is pretty small. We should improve it with several usages, maybe even a demo application, but at the very least there should be a couple of examples on how to use the directive.