for 550 it goes to 523 pixels
Is this a bug
I use chrome 77.0.3865.120.
any update on chrome 78 support by protractor 5.4.2 ?
you could type chrome version that you have at a machine
'chromeOptions': {
'args': [
'--window-size=1281,801',
]
}
'args': [
'--window-size=1281,801',
]
}
@logeshk to get 78 to work for me, I manually update webdriver-manager inside protractor node_modules
To give more context. I want to utilize my page objects across mutiple projects and i dont want the same page objects/common /wrapper functions exist in all the repos
@krish0205 that's probably your best bet to avoid duplicate code. But keep in mind, any time someone updates a page object, all your other projects need to update their package.json version to reference the newest changes, and those changes could break other projects. You also probably don't want your page objects publicly hosted on npmjs.com - we use ProGet to privately host npm packages. If you aren't already, I highly recommend using TypeScript with all your protractor projects / npm libraries. I used typescript-library-starter to easily create an abstract typescript lib I could easily npm install in my other projects
@luker2 Thank you for the information. I'm not hosting them on to npmjs.org. We use internal nexus to host all the npm packages. As you mentioned any chnages to page objects will break the other dependent projects, unless they update package.json. The typescript-library-starter looks promising and might help with my issue.. I will give a shot. Thank you @luker2
@Rahulsh76144034_twitter install the aws-sdk library into your protractor project, then read their docs to find an example of using credentials to first get authenticated to your storage account, then another example of uploading/downloading data. Since these will be async functions, you'll want to call them within protractor's control flow so your tests wait for the data to be retrieved before using it. pseudo-code:
return browser.controlFlow().execute(() => {
return aws.downloadSomething(downloadedData => {
doSomethingWithMyData(downloadedData);
}
})
I want to understand, is there a way where instead of downloading the full json or excel file from AWS bucket, we can fetch the key value to pass as test data from the AWS S3 bucket data file while executing the test case?
@Rahulsh76144034_twitter it sounds like you're trying to store data for ALL test cases in E2Edata.json, but have each test access only the data it needs from the file. That's not possible, instead each test would have to download the entire file, then access the particular data for that test. I'd recommend having separate data files for each test.
ohhkk @krish0205, yes this can help after fetching JSON file. But do you know how to connect with AWS S3 json file directly without downloading the json file in framework folder structure.
Is it possible to make connection with the datafile present in AWS during test case execution?
import TestData from '$e2e/test-data/E2eTestdata.json';
import dataProvider = require('jasmine-data-provider');
describe('Name of the group', () => {
dataProvider(TestData, (data) => {
it('should behave...', () => {
expect((data.KeyValue)).toBe(true);
element(by.id('id')).sendKeys(data.KeyValue1);
});
});
});
you can download the .json file from aws to your repo and try something like above using the jasmine-data-provider
@Rahulsh76144034_twitter I'm not entirly sure of that
I get what you're trying to do, but storing data (individual key/values) in s3 doesn't seem right (or at least makes me think of the increased cost by all the individual data reads by each test). Why not, for each e2e test, 1) download json file 2) read & store in memory 3) execute test steps, accessing the data you need, avoiding multiple calls to s3
I'm having an odd issue running protractor that only occurs in circleci. I was wondering if anyone had any pointers to resolve it.
The suite seems to die after browser is launched and before a test is run.
This is what I see when the browser is firefox:
[22:14:29] I/launcher - Running 1 instances of WebDriver
[22:14:29] I/direct - Using FirefoxDriver directly...
[22:14:52] E/launcher - Error while running testForAngular: JavaScriptError: Document was unloaded
[22:14:52] E/launcher - Error: Error while running testForAngular: JavaScriptError: Document was unloaded
at executeAsyncScript_.then (/app/node_modules/protractor/built/browser.js:727:23)
at ManagedPromise.invokeCallback_ (/app/node_modules/selenium-webdriver/lib/promise.js:1376:14)
at TaskQueue.execute_ (/app/node_modules/selenium-webdriver/lib/promise.js:3084:14)
at TaskQueue.executeNext_ (/app/node_modules/selenium-webdriver/lib/promise.js:3067:27)
at asyncRun (/app/node_modules/selenium-webdriver/lib/promise.js:2927:27)
at /app/node_modules/selenium-webdriver/lib/promise.js:668:7
at processTicksAndRejections (internal/process/task_queues.js:86:5)
[22:14:52] E/launcher - Process exited with error code 199The error is similar when using chrome instead.
I've not seen this issue locally
This is the error in chrome
[19:55:16] I/launcher - Running 1 instances of WebDriver
[19:55:16] I/direct - Using ChromeDriver directly...
[19:55:45] E/launcher - Error while running testForAngular: script timeout
(Session info: headless chrome=78.0.3904.108)
(Driver info: chromedriver=78.0.3904.70 (edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800}),platform=Linux 4.10.0-35-generic x86_64)
[19:55:45] E/launcher - Error: Error while running testForAngular: script timeout
(Session info: headless chrome=78.0.3904.108)
(Driver info: chromedriver=78.0.3904.70 (edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800}),platform=Linux 4.10.0-35-generic x86_64)
at executeAsyncScript_.then (/app/node_modules/protractor/built/browser.js:727:23)
at ManagedPromise.invokeCallback_ (/app/node_modules/selenium-webdriver/lib/promise.js:1376:14)
at TaskQueue.execute_ (/app/node_modules/selenium-webdriver/lib/promise.js:3084:14)
at TaskQueue.executeNext_ (/app/node_modules/selenium-webdriver/lib/promise.js:3067:27)
at asyncRun (/app/node_modules/selenium-webdriver/lib/promise.js:2927:27)
at /app/node_modules/selenium-webdriver/lib/promise.js:668:7
at processTicksAndRejections (internal/process/task_queues.js:86:5)
[19:55:45] E/launcher - Process exited with error code 199
since this is before a test executes, this is likely to deal with the onPrepare statement? This is it:
onPrepare: () => {
jasmine.getEnv().addReporter(myReporter);
browser.get(baseUrl);
browser.manage().window().maximize();
browser.manage().timeouts().implicitlyWait(5000);
return browser.driver.wait(() => {
return browser.driver.getCurrentUrl().then((url: String) => {
return url == baseUrl;
});
}, 10000);
}
Hi all, is there a possibility to chain the conditions on an element once you get it ? For example, instead of inserting two expect statements like this
expect(getSomeElement().isPresent()).toBe(true);
expect(getSomeElement().isDisplayed()).toBe(true);, I would like to use only one 'expect' statement if possible.
