Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config file examples? #13

Open
soundstep opened this issue Oct 25, 2012 · 4 comments
Open

config file examples? #13

soundstep opened this issue Oct 25, 2012 · 4 comments

Comments

@soundstep
Copy link

Hi there,

I just updated bunyip, I run 0.2.2.

I'm not sure I'm set up correctly with browserstack.

I run the following command:

bunyip -f index.html -b ios

With the following config file:

var config = {
    "browserstack": {
        "username": "XXX",
        "password": "XXX",
        "timeout": 480
    },
    "port": 9000,
    "tunnellink": "NAME.pagekite.me",
    "tunnel": "pagekite.py <port> NAME.pagekite.me"
};

module.exports = config;

I also tried (with pagekite running manually):

"tunnel": "show <port> NAME.pagekite.me"

In both case, I get the log:

Creating a Hub. Open yeti --server in another Terminal to reuse browsers for future batches.

Waiting for agents to connect at http://192.168.1.172:9000
...also available locally at http://localhost:9000
When ready, press Enter to begin testing.
null
  BrowserStack iPad 3rd (6.0) 6.0 worker launched: 409331
  BrowserStack iPad 2 4.3.2 worker launched: 409332
  BrowserStack iPad 2 (5.0) 5.0 worker launched: 409333
  BrowserStack iPad 3rd 5.1 worker launched: 409335
  BrowserStack iPad 3.2 worker launched: 409334
  BrowserStack iPhone 3GS 3.0 worker launched: 409336
  BrowserStack iPhone 4S 5.1 worker launched: 409337
  BrowserStack iPhone 4S (6.0) 6.0 worker launched: 409338
  BrowserStack iPhone 4 4.0 worker launched: 409339
  BrowserStack iPhone 5 6.0 worker launched: 409340

But nothing is happening.

If I open a browser on localhost:9000 or NAME.pagekite.me, I can see the connection in the log.
So I guess it is just the browsers in the browserstack VM that are not connecting?

Any idea?

I also don't understand why we need the param "-f index.html" with browserstack.
Is that a file path that is appended to the tunnel?
like: http://NAME.pagekite.me + "/" + "index.html"?

Thanks for any help!

@soundstep
Copy link
Author

In the log it says:

Waiting for agents to connect at http://192.168.1.172:9000

Shouldn't it say this?

Waiting for agents to connect at http://NAME.pagekite.me

@ryanseddon
Copy link
Owner

The BrowserStack workers can sometimes take quite a while to connect, it's still in beta so expect some wonkiness.

Your config is correct.

As for the log this is coming yeti and until they release an update to properly plug into it I'll have little control over what is shown without considerable monkey patching.

I also don't understand why we need the param "-f index.html" with browserstack.

The -f [file path] param is needed so yeti knows which file to load when you kick off a test run.

I'll leave this open an investigate when I get home to see what I can do about the log message.

@soundstep
Copy link
Author

I see, but after 5-10 min I guess it is not going to connect.
If the VM are trying to connect to "http://192.168.1.172:9000"

Waiting for agents to connect at http://192.168.1.172:9000
...also available locally at http://localhost:9000
When ready, press Enter to begin testing.

It is not going to work as this is an IP on my local network.

This sound like an issue, right?

I'm not sure where is the issue thought, is bunyip sending NAME.pagekite.me as a url parameter to the browserstack API (or yeti?)?

Cheers.

Romu

@ryanseddon
Copy link
Owner

So bunyip uses pagekite to create an SSH tunnel to your localhost so NAME.pagekite.me is an internet accessible address pointing to your localhost. Bunyip will always send the SSH tunnel address to browserstack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants