If I understood you correctly, your solution will depend on the type that the “second” function returns. In a nutshell, there are at least 2 ways to do it: Lambda syntax Interfaces (normal and generic interfaces) I’ve tried to explain all these in the code below, please, check it: module main { export class TestClass … Read more
You can try the following: Switch to the new opened tab. Close the current windows (in this case, the new tab). Switch back to the first window. browser.getAllWindowHandles().then(function (handles) { browser.driver.switchTo().window(handles[1]); browser.driver.close(); browser.driver.switchTo().window(handles[0]); });
As of the most recent Protractor (1.6.1 as of this writing), the syntax changed a bit: var row = results[randomNum].element(by.xpath(‘..’)); (use element() instead of findElement()).
This is a rather common problem in test automation with selenium. Here are the common solutions: make sure the element you want to click is actually visible. Sometimes you need to make extra actions on a page to make the element visible. For example, open up a dropdown for an option to appear or open … Read more
You can test Angular 2 applications with Protractor (starting from Protractor 2.5.0). For Protractor 5.0.0+, you don’t have to do anything specific, Protractor will auto-detect the Angular version used in the application under test. For Protractor >= 2.5.0 and <= 4.0.14, you would only need to add useAllAngular2AppRoots: true to your config. Here is a … Read more
Use browser.manage().logs().get(‘browser’) browser.manage().logs().get(‘browser’).then(function(browserLogs) { // browserLogs is an array of objects with level and message fields browserLogs.forEach(function(log){ if (log.level.value > 900) { // it’s an error log console.log(‘Browser console error!’); console.log(log.message); } }); });
I was facing this error too and by the time I read the tutorial, it did not cover how to install protractor and the webdriver as local dependencies to your project (which are located in ./node_modules). If this is what you prefer (probably because you might want to use grunt-protractor-runner and run your test later … Read more
The advantage of separating the child from the child css selector would only be if you’d like to use the parent for something else. Otherwise, it’s slightly faster to do it in one call, like expect(element(‘#parent_1 > .red’)).toBe(‘red’); since Protractor doesn’t need to make two calls to the browser in this case. Another reason to … Read more
You can test whether the element is present with isPresent. Here are the protractor docs for the isPresent function. So, your code would be something like: var myElement = element(by.css(‘.elementClass’)); expect(myElement.isPresent()).toBeFalsy();