Here’s my best to answer your first question, for the two scenarios – If multiple testers run the scripts in their own machine, the helper method can be placed in onPrepare() function assigning the value to a constant global variable, which will be available for all the tests. If all the tests are run on … Read more
1. Regarding with route check In case after first spec, user got logged in and the route changed. Make sure all are navigated before any test executed. expect(browser.getCurrentUrl()).toContain(‘#/the_route_of_logged_in’); // ‘#/’ is just illustration. You can remove it to make it shorter // => like this …toContain(‘the_route_of_logged_in’); 2. Regarding with click on tutorial browser.wait(EC.elementToBeClickable(tutorial), 10000); Do … Read more
You can set ignoreSynchronization to be false once your verification is done. However, note that ignoreSynchronization is synchronous while everything else (click/get/etc) is asynchronous, so you need to be careful with that. Probably the safest way is to set it to true in beforeEach and false in afterEach, and just test that single logo click … Read more
There might be multiple reasons for that and it is going to be a guessing game anyway. it could be that there is an another element matching the .login-button locator and you are clicking a different element. Let’s improve the locator: element(by.css(“.login-form .login-button”)).click(); wait for the element to be clickable: var EC = protractor.ExpectedConditions; element(by.model(‘credentials.username’)).sendKeys(‘RET02’); … Read more
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 elements are returned using … Read more
This will wait for page loads / jquery.ajax (if present) and $http calls, and any accompanying digest/render cycle, throw it in a utility function and wait away. /* C# Example var pageLoadWait = new WebDriverWait(WebDriver, TimeSpan.FromSeconds(timeout)); pageLoadWait.Until<bool>( (driver) => { return (bool)JS.ExecuteScript( @”*/ try { if (document.readyState !== ‘complete’) { return false; // Page not … Read more
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 … Read more