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

After navigating to URL, why don't the browsers let go? #213

Open
djangofan opened this issue Jul 25, 2016 · 0 comments
Open

After navigating to URL, why don't the browsers let go? #213

djangofan opened this issue Jul 25, 2016 · 0 comments

Comments

@djangofan
Copy link

After navigating to URL, why don't the browsers let go? My tests start on Saucelabs (QUnit tests) and the browsers sit there doing nothing until the 3 minute (no activity) timeout is reached and then they finally give up. What am I doing wrong? I am expecting that immediately after the browser navigates to the initial URL, the test should end successfully right there BUT this is not what I see.

I configured my Gruntfile.js like this:

'saucelabs-qunit': {
            all: {
                options: {
                    username: uname,
                    key: ukey,
                    urls: ['http://the-internet.herokuapp.com', 'http://the-internet.herokuapp.com/context_menu'],
                    tunnelTimeout: 5,
                    tunneled: true,
                    build: 'grunt-qunit-1',
                    concurrency: 3,
                    browsers: browsers,
                    testname: 'nav to the-internet',
                    tags: ['master']
                }
            },

And the error I get looks like this, complaining about a 'length' parameter that I presume to be the 180 second timeout value?

>> Local Npm module "grunt-cli" not found. Is it installed?

Running "connect:server" (connect) task
Starting connect web server on localhost:9999.

Running "saucelabs-qunit:all" (saucelabs-qunit) task
=> Starting Tunnel to Sauce Labs
>> Connected to Saucelabs

 1 / 6 tests started

 2 / 6 tests started

 3 / 6 tests started

 4 / 6 tests started

 5 / 6 tests started

 6 / 6 tests started


Tested http://the-internet.herokuapp.com/context_menu
Platform: linux,chrome,latest
Passed: true
Url https://saucelabs.com/jobs/619553d-----------cb94f1052cf69bbc7


Tested http://the-internet.herokuapp.com
Platform: linux,chrome,latest
Passed: true
Url https://saucelabs.com/jobs/306a3f1341f-----------60ddba570dc4


Tested http://the-internet.herokuapp.com
Platform: WIN10,chrome,latest
Passed: true
Url https://saucelabs.com/jobs/8ef4fc368d-----------b22213f04ad8


Tested http://the-internet.herokuapp.com/context_menu
Platform: WIN10,firefox,latest
Passed: true
Url https://saucelabs.com/jobs/cece63c10914-----------08c015fb


Tested http://the-internet.herokuapp.com/context_menu
Platform: WIN10,chrome,latest
Passed: true
Url https://saucelabs.com/jobs/6957ffb353-----------d574fb0716


Tested http://the-internet.herokuapp.com
Platform: WIN10,firefox,latest
Passed: true
Url https://saucelabs.com/jobs/74e747613db-----------050d074fe3e
>> All tests completed with status true
=> Stopping Tunnel to Sauce Labs

Running "saucelabs-qunit:onTestComplete" (saucelabs-qunit) task
=> Starting Tunnel to Sauce Labs
>> Connected to Saucelabs
=> Stopping Tunnel to Sauce Labs
>> TypeError: Cannot read property 'length' of undefined
Warning: Task "saucelabs-qunit:onTestComplete" failed. Use --force to continue.

Aborted due to warnings.
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

1 participant