by

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
Dzanan91
@Dzanan91

Hey guys, I have a problem with running my script. For some reason node_modules folder in my App Data folder is being targeted instead of the one in my project folder when using VS Code terminal. Also it keeps saying my chromedriver is outdated even though i updated it globally and locally.
Using Protractor with Jasmine

https://d.pr/i/taX0zP

Any help would be appreciated

Brandon Gibbons
@GibbsB
@Dzanan91 That error is a mismatch between the chromedriver (v74.0.3729.6) and the chrome browser, which are different things. Try to see which version your chrome browser is in Help -> About Google Chrome. If you have multiple versions of Chrome Browser in your project, you will have to target the right one to match your chromedriver. https://chromedriver.storage.googleapis.com/74.0.3729.6/notes.txt Your chromedriver version only supports Chrome Browser v74. The latest of chromedriver should 80.x.x.x, so you might not be getting the latest with your webdriver-manager update command.
Dzanan91
@Dzanan91
I have latest version of chrome browser
And have installed latest chromedriver stable version ( 79 )
still for some reason doesnt read the latest chromedriver version
and returns error as shown in screenshot above
so weird
Brandon Gibbons
@GibbsB
First thing I would do is remove that global install from that roaming/npm/node_modules directory. Chromedriver 79 definitely shouldn't be returning an error related to Chrome 74
Dzanan91
@Dzanan91
okay let me try that
Thanks
Aasim Anwar
@aasimali
Hi, Would like to know that, can we automate a PDF loaded in browser using Protractor?
hfsoares
@hfsoares
Hello guys, I need some debugging tips. I am using Angular 8, and Google Chrome 80.x.x.x.x
I have a test that logs in the system, by sendKeys for login and password, press a button, and then try to fill 2 more form fields, name and description also with sendKeys.
The script goes well until the last description field, when it freezes.
I have switched the order, filling description first, and the system freezes at the name. So, it seems that my finder is correctly designed.
I am using async and await pattern
Thomas
@selenium4466_gitlab
@hfsoares could you post snippet of code
hfsoares
@hfsoares
Sure
navBarGrupos = new NavBarGrupos();
await navBarGrupos.clickOnCrieNovoGrupo();
grupoUpdatePage = new GrupoUpdatePage();
grupoCabecalhoPage = new GrupoCabecalhoPage();
await grupoUpdatePage.setNomeInput('nome'),
await grupoUpdatePage.setDescricaoInput('descricao')
this is the test.spec (the names are in portuguese)
this is the page finder elements
editForm = element(by.name('editForm'));
nomeInput = this.editForm.element(by.id('field_nome'));
descricaoInput = this.editForm.element(by.id('field_descricao'));
I have tried whitout the editForm, and it behaves the same way
async setNomeInput(nome: string): Promise<void> {
await this.nomeInput.sendKeys(nome);
}
this is the "typer"
Thomas
@selenium4466_gitlab
async setNomeInput(nome: string): Promise<boolean> { await this.nomeInput.sendKeys(nome).then(()=>{ }); }
await grupoUpdatePage.setNomeInput('nome').then(async (value)=>{ await expect(value).toBe(true) });
hfsoares
@hfsoares
I will try that... but why would work?
Thomas
@selenium4466_gitlab
@hfsoares also check element the one you performing an action on
hfsoares
@hfsoares
check?
Thomas
@selenium4466_gitlab
inspect the element the one it freezes
make sure its correct one
hfsoares
@hfsoares
oh, yes, it is te correct one. If I swith the order, then it will be ok
Thomas
@selenium4466_gitlab
is the website public domain or under company proxy?
hfsoares
@hfsoares
company proxy.
.then(async (value)=>{ await expect(value).toBe(true) }); this part here doesn't work, because expect(value).toBe(true) it is not a promise
Thomas
@selenium4466_gitlab
@hfsoares I see in that case its hard to tell what could be a wrong with it
hfsoares
@hfsoares
nobody is complainng about chrome 80? I have just updated
I can share my screen with you.
Thomas
@selenium4466_gitlab
drivers were updated to version 80, which means make sure you have node above 10.15.1 and webdriver-manager 12.7.1 min
also make sure you chrome browser also updated to 80
screenshot would definately help
hfsoares
@hfsoares
node is v12
my browser is 80
let me check the webdriver
Thomas
@selenium4466_gitlab
are you running webdriver-manager update before
hfsoares
@hfsoares
webdriver is 12.1.7
it is the latest
hfsoares
@hfsoares
would you join me in skype?
Vladimir Pozdniakov
@Vladimir-Pozdniakov
Hi guys. I need to replace one of the server responses in my e2e test. How can I do it with Protractor?
Luke
@luker2
@Vladimir-Pozdniakov I've never got it working, but it seems like I've heard of people spinning up a proxy server within protractor's onPrepare function. I assume from there you could capture/modify the traffic going in/out
nunofreitasbotelho
@nunofreitasbotelho

This is my PO:

getTableHeaders() {
    const tableHeaders = [];
    element.all(by.css('.mat-header-cell button')).then(elements => {
      elements.forEach(el => {
        el.getText().then((header: string) => {
          console.log(header);
          tableHeaders.push(header.toUpperCase());
        });
      });
    }).then(() => {
      return tableHeaders;
    });
  }

cant i return the array?

I'm not able to get the array on the test