PhantomJS instance still running when grunt test failed about grunt-mocha-webdriver HOT 9 CLOSED

Yes. The fact that it's still running is a bug... it should be exiting via https://github.com/jmreidy/grunt-mocha-webdriver/blob/master/tasks/grunt-mocha-wd.js#L82. I'm guessing an error is exiting before reaching that code.

from grunt-mocha-webdriver.

Yes, a fatal error is exiting before it reaches that code. Here an output of my grunt test:

$ grunt test:client
Running "env:test" (env) task

Running "clean:test" (clean) task
Cleaning server/var/test/level...OK

Running "start_listen" task

Running "mochaWebdriver:client" (mochaWebdriver) task
Running webdriver tests against PhantomJS.
PhantomJS started.


  Create/Activate/Login (story)
    ✓ valid sign up redirects to activation email page (1962ms)
    ✓ activation will fail when input is correct but code is wrong (909ms)
    ✓ unable to login when not activated yet (913ms)
    ✓ cheat activation and do the login (2602ms)

  Delete account
    ◦ cannot delete with invalid input: Fatal error: expected [Error: Unable to find element with css selector 'fieldset.modal p.warning input[name="confirmEmail"]'] to equal undefined

You see I get a fatal error at the bottom. Where is this coming from? Why fatal? How can I dig deeper here and find the culprit?

from grunt-mocha-webdriver.

It's odd that the error isn't being caught anywhere... looks like it's failing because your code is treating an error as an element. Can you post the test code?

from grunt-mocha-webdriver.

Exactly, it's weird. The test code is the file account.settings.js at https://gist.github.com/binarykitchen/7921116 ...

Any suggestions are very welcome!

from grunt-mocha-webdriver.

I'm not seeing the same test steps in the Gist as are included in the
broken test output...

On Saturday, December 14, 2013, Michael Heuberger wrote:

Exactly, it's weird. The test code is the file account.settings.js at
https://gist.github.com/binarykitchen/7921116 ...

Any suggestions are very welcome!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-30595783
.

from grunt-mocha-webdriver.

@jmreidy I think I am doing something completely wrong. That's why I need your feedback on that gist. And I also would love to see real good e2e examples in the wild based on grunt-mocha-webdriver.

Any chance you can help me with that soon?

from grunt-mocha-webdriver.

@jmreidy Ping? Or too busy buying xmas presents eh? :)

from grunt-mocha-webdriver.

Did some research without success. Something smells here. Somehow fatal errors crash everything. Difficult to say. Really would love to see good e2e examples here ...

from grunt-mocha-webdriver.

Just checking: do you quit the browser when any error occur?

Like this inside Mocha?

  after(function() {
    return browser.quit();
  });

from grunt-mocha-webdriver.