Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 19:00
    tfaron commented #5133
  • Jan 31 2019 07:28
    cnishina closed #5135
  • Jan 31 2019 07:28
    cnishina commented #5135
  • Jan 30 2019 16:23
    ThabisoGithub closed #5136
  • Jan 30 2019 16:23
    ThabisoGithub edited #5136
  • Jan 30 2019 16:23
    ThabisoGithub edited #5136
  • Jan 30 2019 16:21
    ThabisoGithub opened #5136
  • Jan 30 2019 16:18
    IgorSasovets commented #4177
  • Jan 30 2019 15:05
    andrewchan-clover commented #4177
  • Jan 30 2019 13:43
    IgorSasovets commented #5135
  • Jan 30 2019 12:37
    EnzDev edited #5125
  • Jan 30 2019 11:47
    akshaymondal opened #5135
  • Jan 29 2019 14:33
    uinest commented #4822
  • Jan 28 2019 21:38
    cnishina commented #5132
  • Jan 28 2019 21:37
    cnishina commented #5134
  • Jan 28 2019 21:37
    cnishina closed #5134
  • Jan 28 2019 21:36

    cnishina on selenium4

    chore(release): bumpb version t… (compare)

  • Jan 28 2019 11:30
    think4ideas opened #5134
  • Jan 28 2019 11:01
    toniedzwiedz commented #2735
  • Jan 28 2019 09:42
    azorrozua commented #4786
Yogendra Porwal
@yogibaba2
hello /@all I have improvised an html reporter for protractor with jasmin, it also combined a console reporter.
please try once and let me know the feedback
note: its just an improvisation
https://www.npmjs.com/package/protractor-jasmine2-html-cli-reporter
Shatha-Alhamad
@Shatha-Alhamad
hi all , please any idea how to write protractor test for auto checking backend error logs and extracting the logs related to prod server ? thanks
jedwantstocode
@jedwantstocode
has anyone encountered running webdriver-manager start in jenkins and it hangs and does not continue with test
no error even after 5mins
Sri Harsha
@harsha509
Hi @jedwantstocode providing jenkins log might help us to debug the issue.
jedwantstocode
@jedwantstocode
good morning all. Currently, when I run my tests locally, the login credentials(username, password) is in a json file and it is gitIgnored so it wont be uploaded to the public repo. I wanted to run my tests in jenkins, is there a way to handle this where I dont have to upload the username and password to the app but enable login during my test?
@Harsha509 Hi sri, I updated my test to use the standalone server and commenting out the selenium address in my conf. it did run my test but just realized now that jenkins does not allow me to manage the app when its inside the iframe
Sri Harsha
@harsha509
okay, so if you dont want to upload your credential file. try to encrypt the credentials and decrypt when you want to use
Sri Harsha
@harsha509
This package might help you https://www.npmjs.com/package/encryptjs
Mayank Verma
@mayankverma24
Hi All, is there a way to access the cookies through xmlhttprequest method?
Sri Harsha
@harsha509
@mayankverma24 Have you tried => var cookie = XMLHttpRequest.getAllResponseHeaders(Set-Cookie);
or Set-Cookie2
Mayank Bhola
@psych0der
Hello there. I have submitted a PR here at angular/protractor#5260. I have tried signing CLA multiple times but still it shows no-cla. Can anybody help me here?
jbittmansb
@jbittmansb
Hi, I am struggling to find how to select elements in native app thru appium using accessibility id. the global.by object has no locator by accessibility id. Is this not supported thru protractor and I should use a different locator type?
jedwantstocode
@jedwantstocode
Hi @Harsha509 again! thank you. I will look into that and come back. Btw, our application uses the microsoft login service and then after successful login, it loads the application. I hope your link will help with that.
hi @Harsha509 , Im sorry, to encrypt I still have the push my code with my actual username and password?
Sri Harsha
@harsha509
hi @jedwantstocode, No Need to, you can first encrypt credentials in your local machine and provide pass the encrypted passphrase and secret-key in your scripts. Which you can decrypt in your scripts where ever required
jedwantstocode
@jedwantstocode
with the encrypted string, I can use that in place of the password in my normal json file where I usually store my password?
@Harsha509
Sri Harsha
@harsha509
Yes, you can use encrypted string and decrypt when you want to use original password
Aasim Anwar
@aasimali
image.png
image.png

Dear All,

Can someone check my code and tell me, please, why isSelected returning 'false'?

it("Filter Test", function(){
browser.get("https://www.osianama.com/indian-asian-antiquities-arts/armour-helmets");
let artwork = element(by.xpath("//div[@class='c-btn form-control'][span[text()='Artwork Title']]")).click();
browser.sleep(3000);

let checkbox = element(by.xpath("//label[text()='Akoda-Nari Kabuto (2)']"));
checkbox.click();
expect(checkbox.isSelected()).toBe(true);

    }); // end of it
jedwantstocode
@jedwantstocode
@Harsha509 will they be able to decrypt my password, using the same tool, since they will see it once I upload in git?
Sri Harsha
@harsha509
Yes then can, if they only know the secret code used for encryption
barret-p
@barret-p
Hello, what is the purpose of this line? https://github.com/angular/protractor/blob/cc501f71bc1f995a83c1041e1aa489ea0f105679/lib/launcher.ts#L210 What is the purpose of forking only when totalTasks > 1? In my case, I would like to fork even when running only a single spec file. The output format of the logs is different whether forkProcess is true or not. I would like it have consistent output format regardless of tests or suites run.
Star Yznaga
@wyznaga
Is there support existing or planned for running Protractor specs/parts of specs only for components that actually changed in the current commit, sort of like when using the Jest CLI with --changedSince or --onlyChanged?
Lorenzo Urbini
@siteriaitaliana
i'm building a docker image but after migrating to protractor@6.0.0 I've started to get:
E/launcher - Error: WebDriverError: unknown error: Chrome failed to start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
any idea of the reason? also why is 6.0.0 not marked as stable yet?
nbuso
@nbuso
Hi everyone, I'm in a strange situation where protractor seem not updating the update-config.json files. What's happening is my version of Chrome is newer and in chrome-response.xml there are newer versions of chromedriver, but update-config.json is poiting to an older version. Why webdriver-manager is no updating update-config.json? Below the tipical error running ng e2e:
[13:54:05] I/config_source - curl -o/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/protractor/node_modules/webdriver-manager/selenium/chrome-response.xml https://chromedriver.storage.googleapis.com/
ℹ 「wdm」: Compiled successfully.
[13:54:05] I/update - chromedriver: file exists /home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_74.0.3729.6.zip
[13:54:05] I/update - chromedriver: unzipping chromedriver_74.0.3729.6.zip
[13:54:05] I/update - chromedriver: setting permissions to 0755 for /home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_74.0.3729.6
[13:54:05] I/update - chromedriver: chromedriver_74.0.3729.6 up to date
[13:54:06] I/launcher - Running 1 instances of WebDriver
[13:54:06] I/direct - Using ChromeDriver directly...
[13:54:06] E/launcher - session not created: This version of ChromeDriver only supports Chrome version 74
  (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Linux 5.2.7-200.fc30.x86_64 x86_64)
[13:54:06] E/launcher - SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 74
  (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Linux 5.2.7-200.fc30.x86_64 x86_64)
    at Object.checkLegacyResponse (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/selenium-webdriver/lib/error.js:546:15)
    at parseHttpResponse (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/selenium-webdriver/lib/http.js:441:30)
    at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
    at Function.createSession (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/selenium-webdriver/chrome.js:761:15)
    at Direct.getNewDriver (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/protractor/built/driverProviders/direct.js:77:33)
    at Runner.createBrowser (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/q/q.js:834:54)
    at /home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/q/q.js:863:30
    at Promise.promise.promiseDispatch (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/q/q.js:796:13)
    at /home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/q/q.js:556:49
    at runSingle (/home/nbuso/projects/ebeye-local/src/ebinocle-webjs/node_modules/q/q.js:137:13)
[13:54:06] E/launcher - Process exited with error code 199
nbuso
@nbuso
chromedriver is available also for version 77, but protractor stick with 74! any idea?
Tedi Roca
@tedi.roca_gitlab
@nbuso upgrading webdriver-manager manually should allow you to use the latest chromedriver
nbuso
@nbuso
@tedi.roca_gitlab no if run webdriver-manager update it keep dowloading version 74
Tedi Roca
@tedi.roca_gitlab
running this command will update chromedriver, but not the wedriver-manager itself
there was a bug with the webdriver-manager not including the latest version of the chromedriver
running npm install -g webdriver-manager@lates and then wedriver-manager update should fix it
nbuso
@nbuso
I'm version on 5.4.2 that is the latest if I'm not wrong
Tedi Roca
@tedi.roca_gitlab
protractor installs webdriver-manager as dependency, and in that case the webdriver-manager that is installed does not allow installing the lastest chromedriver
the webdriver-manager itself can be installed and updated manually to get the latest version
nbuso
@nbuso
alright, I will try and this mean I need to change my CI/CD pipeline... let's see
Tedi Roca
@tedi.roca_gitlab
yep - not ideal, but it seems this is the only solution until the dependency is updated
here you have more info: angular/webdriver-manager#404
nbuso
@nbuso
uhm! how do you make protractor pointing to the global installed webdriver in standalone mode? do I need to set the chromedriver and geckodriver path manually?
Tedi
@tediroca
in my case protractor directly uses the globally installed version, but if this does not work you can always navigate to the node_modules directory where the webdriver-manager dependency was installed when installing protractor and update that local version
nbuso
@nbuso
yes I updated the local version to test for now, the global version was not picked
nbuso
@nbuso
@tediroca thanks for pointing out the ticket
Pedro Hyvo
@pedrohyvo
Hey guys, I'm facing with the following issue: [09:52:05] E/launcher - session not created: This version of ChromeDriver only supports Chrome version 74 (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Windows NT 10.0.18362 x86_64) [09:52:05] E/launcher - SessionNotCreatedError: session not created: This version of ChromeDriver only supports Chrome version 74 (Driver info: chromedriver=74.0.3729.6 (255758eccf3d244491b8a1317aa76e1ce10d57e9-refs/branch-heads/3729@{#29}),platform=Windows NT 10.0.18362 x86_64)
Does anyone here has any thoughts?
Tedi
@tediroca
Hi @pedrohyvo . Latest versions of Chrome are not supported through the chromedriver versions installed via the webdriver-manager version that Protractor 5.4 installs. There is more info and a workaround in angular/webdriver-manager#404
Pedro Hyvo
@pedrohyvo
@tediroca thanks
Tedi
@tediroca
you are welcome!
Julian Didier
@theredfish
Hello o/
I'm trying to undestand why I can't use the webDriverProxy with the http protocol and seleniumAddress with the https one? Is there someone who know it works by any chance? I'm getting an EPROTO error.