protractor

问题 I am new in Protractor. And I am doing tests to be familiar with it. Here, I met a problem what I cannot distinguish between ignoreSynchronization and async/await method. I had 3 blocks to test them. The first is clear with protractor's own async features. it('without await and ignoreSynchronization', async function() { await browser.waitForAngularEnabled(false); await browser.driver.get('https://www.baidu.com'); console.log('1'); element(by.css('#kw')).sendKeys('protractor').then(() => {

问题 How can I test if an input field is infocus with protractor? I'm doing this: it('should focus email field', function(){ expect(element(by.model('login.email')).getAttribute('id')).toEqual(browser.driver.switchTo().activeElement().getAttribute('id')); }); This seems to work with chrome, but this test fails with firefox. Any ideas? This is the failure message: [firefox #1] 2) Login page should focus email field [firefox #1] Message: [firefox #1] Expected 'login' to equal ''. [firefox #1]

问题 When running end to end tests inside a docker container we need the browser to be wide, to make sure the elements (aButton) that are positioned far right are actually visible and test like expect(mainPage.aButton.isDisplayed()).toBeTruthy(); succeed. When displaying the browser width we always get a value close to 1050 as a maximum: browser.driver.manage().window().getSize().then(function(size) { console.log('browser size', size); }); displays: browser size { height: 748, width: 1050, class:

问题 I am trying to load Firefox to test my web application using selenium. I am getting SessionNotCreatedError: Unable to create new service: GeckoDriverService error when I specify firefox in the capabilities . Here is how it looks like: var config = { sauceUser: process.env.SAUCE_USERNAME, sauceKey: process.env.SAUCE_ACCESS_KEY, framework: 'jasmine2', capabilities: { browserName: 'firefox', version: '57.0', 'screenResolution': '1920x1440' }, specs: [ '*.spec.js' ], jasmineNodeOpts: { showColors

问题 Why we need element(...).getWebElement() over element(...) when both works exactly the same Why two APIs for the same functionality 回答1: Protractor is a convenient wrapper around WebDriverJS - javascript selenium bindings. element(...) would result into an ElementFinder instance introduced in Protractor element(...).getWebElement() would result into a WebElement instance from WebDriverJS . Basically, this gives you access to the pure "bare-metal" WebElement . The most common use-case for

问题 Why we need element(...).getWebElement() over element(...) when both works exactly the same Why two APIs for the same functionality 回答1: Protractor is a convenient wrapper around WebDriverJS - javascript selenium bindings. element(...) would result into an ElementFinder instance introduced in Protractor element(...).getWebElement() would result into a WebElement instance from WebDriverJS . Basically, this gives you access to the pure "bare-metal" WebElement . The most common use-case for

问题 Why we need element(...).getWebElement() over element(...) when both works exactly the same Why two APIs for the same functionality 回答1: Protractor is a convenient wrapper around WebDriverJS - javascript selenium bindings. element(...) would result into an ElementFinder instance introduced in Protractor element(...).getWebElement() would result into a WebElement instance from WebDriverJS . Basically, this gives you access to the pure "bare-metal" WebElement . The most common use-case for

问题 Why we need element(...).getWebElement() over element(...) when both works exactly the same Why two APIs for the same functionality 回答1: Protractor is a convenient wrapper around WebDriverJS - javascript selenium bindings. element(...) would result into an ElementFinder instance introduced in Protractor element(...).getWebElement() would result into a WebElement instance from WebDriverJS . Basically, this gives you access to the pure "bare-metal" WebElement . The most common use-case for

问题 I am assuming that browser.wait should be a blocking call, but it is not working as I expected. Here is my sample: describe("browser.wait", function() { beforeEach(function() { browser.wait(function() { console.log('1 - BeforeEach WAIT'); return true; }); console.log('2 - BeforeEach after wait'); }); afterEach(function() { browser.wait(function() { console.log('4 - afterEach WAIT'); return true; }); console.log('5 - afterEach after wait'); }); it('should probably actually wait.', function() {

问题 I am assuming that browser.wait should be a blocking call, but it is not working as I expected. Here is my sample: describe("browser.wait", function() { beforeEach(function() { browser.wait(function() { console.log('1 - BeforeEach WAIT'); return true; }); console.log('2 - BeforeEach after wait'); }); afterEach(function() { browser.wait(function() { console.log('4 - afterEach WAIT'); return true; }); console.log('5 - afterEach after wait'); }); it('should probably actually wait.', function() {