by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 07:26
    khyati2010 opened #5875
  • 01:54
    jags14385 commented #5668
  • Sep 17 17:42
    alecf opened #5874
  • Sep 17 16:22
    takeya0x86 commented #5380
  • Sep 17 15:31
    codecov[bot] commented #3708
  • Sep 17 15:31
    codecov[bot] commented #3148
  • Sep 17 15:31
    codecov[bot] commented #5040
  • Sep 17 15:25
    jsf-clabot commented #5873
  • Sep 17 15:25
    RimantasDob opened #5873
  • Sep 17 14:43
    AutomationReddy commented #4401
  • Sep 17 14:23
    christian-bromann labeled #5672
  • Sep 17 14:23
    christian-bromann labeled #5672
  • Sep 17 14:13
    sarathps93 commented #5672
  • Sep 17 14:13
    sarathps93 unassigned #5672
  • Sep 17 14:13
    sarathps93 commented #5672
  • Sep 17 12:37
    seanpoulter commented #5668
  • Sep 17 12:32
    christian-bromann synchronize #5804
  • Sep 17 12:32

    christian-bromann on cb-remove-babel

    update deps (compare)

  • Sep 17 11:36
    koggdal commented #5865
  • Sep 17 11:23
    christian-bromann review_request_removed #5804
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
but now I see I never called the kill
and I'm now only trying to do it, but I'm having a hard time with it.
Not sure what I should kill, and how to passit around from onPrepare to onComplete
I thought that just assigning a global 'seleniumStandaloneChild' variable in: seleniumStandalone.start({}, function (err, child) { seleniumStandaloneChild = child; })
I will be able to access it in onComplete
Christian Bromann
@christian-bromann
@csoete the runner takes care of initialising and ending the selenium session, without it you have to do it by yourself
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
but it seems to be null in the 'after'
csoete
@csoete
@christian-bromann I undestand, just wondering because you just wrote that you want to remove the method. But if you are using the driver standalone it would be required. Just confused.
Christian Bromann
@christian-bromann
@csoete sorry about that. I would only remove it if someone uses the wdio test runner
csoete
@csoete
ah ok
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
aha! It seems that what I assign in 'onPrepare:' is not visible in onComplete!
do they run in some separate memory or so?
or am I missing out some obvious node.js workings
how can I pass a value between onPrepare and onComplete?
Christian Bromann
@christian-bromann
@slawomir-brzezinski-at-travcorp I guess you need to assign the child process to a global variable like: GLOBAL.seleniumStandalone = selenium.start ...
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
@christian-bromann . I tried that to no-avail. Maybe I'm missing something obvious
but to be precise, from the docs, I only have access to the process to kill in callback to start - like here: https://github.com/vvo/selenium-standalone#seleniumstartopts-cb
and over there, in the callback, if I do child.kill(), it works
but that's obviously premature :)
it seems like that runs in some separate scope/memory
Tony Keith
@onewithhammer

I'm using grunt + grunt-webdriver + saucelabs + sauceconect. When I run 1 file everything works file but when I try to run 2 files for same I get the following error:
`Running "webdriver:ieexample" (webdriver) task

Grunt Saucelabs Test for Web Driver IO - Tutorial Test Page Website

✓ should be load correct page and title (2499ms)

Title Test for Web Driver IO - Tutorial Test Page Website

✓ should be load correct page and title (1141ms)

Copyright Test for Web Driver IO - Tutorial Test Page Website

1) should be load correct page and title

2) should contain Copyright text

3) should contain Copyright text

2 passing (5s)

3 failing

1) Copyright Test for Web Driver IO - Tutorial Test Page Website should be load correct page and title:

 Uncaught RuntimeError

 Problem: The command you just sent (POST url) has no session ID.

This is generally caused by testing frameworks trying to run commands after the conclusion of a test.

For example, you may be trying to capture a screenshot or retrieve server logs after selenium.stop() or driver.quit() was called in a tearDown method.

Please make sure this process happens before the session is ended.

 Callstack:

-> url("http://www.tlkeith.com/WebDriverIOTutorialTest.html")
`

Tony Keith
@onewithhammer
Nevermind...I found the issue
Christian Bromann
@christian-bromann
cool
just read the text
hellis007
@hellis007
ERROR: Cannot read property 'expectationResultHandler' of undefined
browserName: "chrome". I extremely new to this project and was wondering if I could some assistance with the following error. I'm trying to run jasmine from the wdio.conf.js file I getting the following error. I tried changing the browserName to Firefox and even phantomJS. I'm sure it's something simple I'm missing. Any help would be greatly appreciated. Thanks
Christian Bromann
@christian-bromann
interesting, you pointed out a bug .. I am gonna file an issue
please add jasmineNodeOpts to your wdio conf
even if it is an empty object
hellis007
@hellis007
ok, will do. let me give it a try! thanks
worked like a charm! my test runner is going through fine.
Christian Bromann
@christian-bromann
issue created webdriverio/webdriverio#691
hellis007
@hellis007
thanks christian
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
Hey @christian-bromann . The reason for my yesterday's problem was onComplete not firing. And the reason behind that capabilities had an invalid falsy entry created by: [, { browserName: 'chrome' }] (note the comma).
(It was left by some hasty trimmings of the sample project by fellow dev. Seriously! :smile: )
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
nevertheless, I guess caps could use some removal of falsies, because it seems that the underlying infrastructure doesn't mind them (the tests were running fine)
Johan Thallauer
@JohanTh

hello, when I try to search for a dom element that has been removed:

return this.client
    .waitForExist("selector", undefined, true)
    .should.eventually.be.true;

I get:

AssertionError: expected undefined to be true
Christian Bromann
@christian-bromann
return this.client
    .isExisting("selector")
    .should.eventually.be.false;
Johan Thallauer
@JohanTh

@christian-bromann that gives me

AssertionError: expected true to be false

Christian Bromann
@christian-bromann
then the selector wasn’t removed from the page :wink:
Johan Thallauer
@JohanTh
I can inspect the element in the mirror after this step fails and see that it is gone :worried:
Christian Bromann
@christian-bromann
ok, try this:
return this.client
    .waitForExist("selector", 5000, true)
    .should.eventually.be.true;
this increases the timeout
Johan Thallauer
@JohanTh

that still gave me:

AssertionError: expected undefined to be true

Christian Bromann
@christian-bromann
mhm..and how about:
return this.client
    .waitForExist("selector", 5000, true)
    .isExisting("selector")
    .should.eventually.be.false;
Johan Thallauer
@JohanTh
oh no, sorry, the problem is that I'm an idiot. I had two steps with almost identical names who was doing checks on the same element. What's in the cheat sheet works.
Miguel Rivera
@miguelrivera
Guys, does anyone know how to set a certain screen resolution when using phantomjs? I suspect it must be some capability one adds, right?