by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Erwin Heitzman
    @erwinheitzman
    so that it can be reached
    Ben Siggery
    @siggerzz
    like --bind-address=127.0.0.1:8181 ?
    Erwin Heitzman
    @erwinheitzman
    you could try that but I don't think you need to bind anything, it depends on what you are running in the container, where webdriverio is running and where your application / backend is running
    Ben Siggery
    @siggerzz
    Yeah, I did think it was a bit odd.
    Erwin Heitzman
    @erwinheitzman
    I have to go offline now but if you could share more info about the way you run your setup I can get back to you when I can
    Ben Siggery
    @siggerzz
    Sure thing, no worries. I'm finishing for the day too :)
    Erwin Heitzman
    @erwinheitzman
    enjoy your evening then :)
    Tânia P
    @ButeoButeo
    what is missing me to finally run the test on MacOS? ERROR @wdio/local-runner: Failed launching test session: Error: Couldn't find plugin "html" reporter, neither as wdio scoped package "@wdio/html-reporter" nor as community package "wdio-html-reporter". Please make sure you have it installed!
    Erwin Heitzman
    @erwinheitzman
    Hi @ButeoButeo that an issue unrelated to this service but it means that the reporter is added in your configuration but not installed
    Tânia P
    @ButeoButeo
    @erwinheitzman already installed but still have this other ERROR @wdio/local-runner: Failed launching test session: TypeError: ReporterClass is not a constructor
    at BaseReporter.initReporter....
    maybe my @wdio/local-runner is not proper installed
    Tânia P
    @ButeoButeo
    and this one ERROR @wdio/cli:utils: A service failed in the 'onPrepare' hook
    Error: Unable to connect to selenium
    at Timeout.hasStarted [as _onTimeout]
    Erwin Heitzman
    @erwinheitzman
    Seems like there's more problems with your setup then just a missing package but again it's not related to this service
    Tânia P
    @ButeoButeo
    @erwinheitzman yep, seems to be the setup.... Thanks!
    Riain Condon
    @Stetchy
    Hey @erwinheitzman, have you used this in Browserstack? I have it set up and it works with the WDIO runner locally and works fine with chrome/firefox on Browserstack but Safari doesn't seem to like it at all and just fails calling it. Just wondering if there's any workarounds that have to be done for Safari in Browserstack?
    Erwin Heitzman
    @erwinheitzman
    @Stetchy no because wiremock only allows you to stub a locally running app
    this isn't due to this service but due to the nature of how it works
    Riain Condon
    @Stetchy
    We use browserstack local, so we run our app, parallel to wdio/wiremock and we allow Browserstack to access our local network so it can test our app and access wiremock
    Erwin Heitzman
    @erwinheitzman
    So everything is running on localhost?
    browserstack local only bypasses organisation's proxies
    so it really depends on if it's running on localhost or not
    because wiremock is running on the machine you run your test on, it needs to have the app running on that same machine
    at least that's the basic usage, there might be ways to set wiremock up differently but I'm not familiar with all the settings
    this is just a wrapper for ease of use and you can do everything with this service that you can do with wiremock standalone
    Riain Condon
    @Stetchy
    yeah, so in our jenkins pipeline we run our tests by: building the app, serving the built app, then in parallel to the app being served we run webdriverio with wiremock and browserstack, so in browserstack it uses the app running on localhost and can access wiremock in every browser but safari
    was just wondering if you had encountered it but no worries :) safari is a constant struggle haha
    Erwin Heitzman
    @erwinheitzman
    @Stetchy oh don't get me started haha, there's two ways to look at it though. they are spec compliant and their reasoning is that if others want Apple to implement something then Apple says that it should be added to the webdriver spec. Which is totally fair!
    Also keep in mind that Apple is a hardware manufacturer and not so much software
    The other side is the side of the software manufacturers who try to innovate and help people by filling gaps that are noticed by the community
    It's a constant battle that way which I would think is a double edged sword
    But a good thing in general
    @Stetchy what's your specific issue with WireMock + Safari though?
    Riain Condon
    @Stetchy
    Yeah, I get you. To be fair Apple most of the time do listen but time to implement is longer than for other places but look at least I don't have to use IE... yet...
    So, when I call a mocked API in the UI, in firefox/chrome works fine and as expected, but in Safari for whatever reason the call fails
    Erwin Heitzman
    @erwinheitzman
    IE is actually not that bad (at least from my experience which was like 2 - 3 years ago)
    Riain Condon
    @Stetchy
    But it's really weird, because there's no real evidence of any call happening in the browserstack network logs, sometimes there's an options request which is successful but never any get/post requests, so not sure where it is actually failing
    and because of the way safari handles automation, if I try to check network logs within safari while it's running an automated test, an alert box pops up and I can only either continue the automation or stop it completely
    Erwin Heitzman
    @erwinheitzman
    hmm I honestly don't know either :O
    Erwin Heitzman
    @erwinheitzman
    @Stetchy did you manage to figure out what was wrong?
    Dung
    @Nguyen1412_gitlab
    Just found that WDIO released new version contained mock service as cypress: https://webdriver.io/docs/mocksandspies.html#creating-a-mock
    Hung
    @hunghkit
    Hi all, anyone in here get a problem on android? I'm using wdio-wiremock-service, but got a problem on android. As you know, can't call api as localhost, can't call api localhost:8080
    Erwin Heitzman
    @erwinheitzman
    @hunghkit are you using this with WebdriverIO v5?
    Hung
    @hunghkit
    hi @erwinheitzman , I'm using WebdriverIO v6, it's 6.3.6
    I have a once more question, the lib support AWS and how to configuration on AWS Device Farm? it ran well con iOS, but can't run on iOS in AWS Device Farm :(
    btw, thank for your reply, @erwinheitzman ;)
    Erwin Heitzman
    @erwinheitzman
    @hunghkit Hmm it should work fine for V6 though I haven't been active with the development for a few weeks. Could you share your setup by sharing a Github repo for example so I can debug?
    Regarding AWS, WireMock can only mock requests on localhost so that be why it's not working in the cloud?
    This service was created before we had plans to create a universal network stubbing solution for WebdriverIO. I would advice to that that over this service for that reason :)
    Hung
    @hunghkit
    hi @erwinheitzman
    I found a reason, can't use api as localhost:8080 on android, so I changed to IP of machine, so it worked
    Erwin Heitzman
    @erwinheitzman
    @hunghkit awesome to hear and great debugging :)