This blog post discusses advance usage scenarios for Protractor. In particular it covers the the little know addMockModule() method of the Protractor browser object. The method allows you to create angular modules in Protractor (i.e. mocks or stubs of your API module) and upload them to the browser to replace the real implementation within the … Read more
In the following I list a set of potential causes and possibilities to fix/resolve them. How does AngularJS and Angular(2) Work / What can I check in the Browser Dev Mode I can’t explain it as well as Andrey Agibalov in his Blog here, so check it out (also for developers). Basically, the objects required … Read more
You need to wait for the promise to be solved. The following example comes from an open issue browser.executeScript(‘window.scrollTo(0,0);’).then(function () { page.saveButton.click(); }) Update: This is an old question (May of 2014), but still it is getting some visitors. To clarify: window.scrollTo(0, 0) scrolls to the top left corner of the current page. If you … Read more
If you are behind a proxy, set it correctly in npm. >npm config set proxy http://proxyhost:proxyport >npm config set https-proxy http://proxyhost:proxyport Notes: For SSL/https proxies, the protocol in URL should be http not https If your set up is on a Docker/Vagrant instance or a hosted VM, use IP address instead of hostname for proxy … 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
Suites are incredibly useful for organizing your tests. The question actually goes down to differences between a suite and a test case in general. Quote from the wikipedia “Test suite” definition: a collection of test cases that are intended to be used to test a software program to show that it has some specified set … 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]); });
Depending on what you want to do, you can try: browser.waitForAngular(); or btnLoginEl.click().then(function() { // do some stuff }); to solve the promise. It would be better if you can do that in the beforeEach. NB: I noticed that the expect() waits for the promise inside (i.e. getCurrentUrl) to be solved before comparing.
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