test(multi): added Internet Explorer 11 to ciConf.js (SauceLabs)

[elgalu]

I think we should be testing protractor against IE for every change since it's still a very active browser and I also think IE11 is a good start since is a modern browser that auto-updates plus angular 2.0 will support it

Side note, running npm test against IE11 allowed me to confirm an issue I was having previously: #778

[KasMA1990]

IE11 is probably a bad idea for now as there are some issues with it and Selenium, but the ball is in Microsoft's court at the moment.
https://code.google.com/p/selenium/wiki/InternetExplorerDriver#IE_11_Support

[elgalu]

The only npm test failing locally on IE11 is the one related to getCurrentUrl() so either fixing that issue or skipping it for IE, as we already do on our test suites, should allow to have it on the default test stack IMHO
UPDATE:
Changing from getCurrentUrl() to getLocationAbsUrl() should be enough on IE.

[elgalu]

Also, documentation states IE is a supported browser so we should be testing it right?
https://github.com/angular/protractor/blob/master/docs/faq.md#which-browsers-are-supported
https://github.com/angular/protractor/blob/master/docs/browser-setup.md#browser-support

[juliemr]

Agreed, we should be testing on it. I have worries that it will be flaky (as @KasMA1990 mentions), but it's better to know about failures. I'm concerned about the timeout-death though - asking Travis to re-run now.

[elgalu]

Yes, i'm not sure why it timed out on Sauce Labs because locally worked fine except for the getCurrentUrl() known IE bug.
This is the case where travis_retry may become handy but i see your point on waiting 30mins there, it is an unfortunate long delay :(

[elgalu]

Oh i see the failure is similar again. I'll try to investigate a bit more, until there merging this one is probably not a good idea right now.