end-to-end

I've been trying to handle the basic authentication during my protractor test. Some hard time on it, so i've found a chrome plugin wich sends automatically my credentials for websites that require basic authentication. As each time that chromedriver is executed, a new profile is loaded, how can i permanelty add a plugin to my tests? I know that there is https://sites.google.com/a/chromium.org/chromedriver/extensions , but i dont think this very clear. You need to configure extensions list inside chromeOptions : capabilities { 'browserName': 'chrome', 'chromeOptions': { 'extensions': ['base64

In protractor, there are, basically, 3 ways to check if an element is present: var elm = element(by.id("myid")); browser.isElementPresent(elm); elm.isPresent(); elm.isElementPresent(); Are these options equivalent and interchangeable, and which one should be generally preferred? All function in a similar way with subtle differences. Here are few differences that i found - elm.isPresent() - Is an extension of ElementFinder and so waits for Angular to settle on page before executing any action. It works when elm is an element(locator) or ElementFinder and not ElementArrayFinder . If multiple

I have a SPA application on stack ASP MVC + AngularJS and I'd like to test the UI. For now I'm trying Selenium with PhantomJS and WebKit drivers. This is a sample testing page - view with single element. The list items <li> load dynamically from server and are bounded by Angular. <div id="items"> <li>text</li> <li>text2</li> </div> I'm trying to pass a test and there is an error in this line: _driver.FindElements(By.TagName('li')) At this point there are no loaded elements and _driver.PageSource doesn't contain elements. How can I wait for the items to load? Please do not suggest Thread.Sleep(

I have seen it so many times where people suggest to use: browser.ignoreSynchronization=true; // or false But I do not understand why do we need it? The simple answer is that it makes protractor not wait for Angular promises, such as those from $http or $timeout to resolve, which you might want to do if you're testing behaviour during $http or $timeout (e.g., a "loading" message), or testing non-Angular sites or pages, such as a separate login page. For example, to test a button that sets a loading message during a request you can set it to true when fetching an element + checking its contents