Webdriver asynchronous behaviour is inconsistent using the API about mochify.js

[mantoni]

Interesting. I agree that the API should behave consistently here. Fancy looking into it and sending a patch?

[eskatos]

Not so much, but here are some more details.

To handle errors properly (gulp return !=0 on test failure, or, on any other failure) I had to register two calbacks. When the error reason is test failure, then both of the callbacks are called causing a warning in gulp. Not a blocker and node/phantom/webdriver consistent.

Using webdriver, I could not find a callback that's triggered after the tests hence the gulp task marked as finished too soon. Finding a way would provide a workaround. Any clue?

Did you reproduce the described behaviours using the sample project?

[mantoni]

Sorry, but I have no time / motivation in fixing issues that arise from this use case. I will assist, merge and release a patch if anyone volunteers.

[eskatos]

No problem. I can put some cycles trying to understand at first.

Writing helps. I reviewed my sample project and removed xunit reporter and reports collection. This has nothing to do with this issue. Moreover, I was wrong about error handling, a single callback is enough. Sorry for the noise.

I now suppose that when using webdriver the bundle() method returns something (stream,promise?) that ends prematurely. Does that makes any sense to you?

[mantoni]

Sure, makes sense. What is returned by Mochify is the Browserify instance with an "enriched" pipeline. The plugin that gets added into the pipeline for webdriver tests is min-webdriver. Maybe you can find something in there.

[eskatos]

Thanks for the pointers Maximilian. I had the same feeling, the culprit seems to be in min-webdriver.

Unfortunately I'm not up to speed when it comes with the js ecosystem and don't have much free cycles myself.

At least the issue is documented now.

[mantoni]

There was some refactoring lately regarding error handling and also in the webdriver module. This might have fixed the issue. @eskatos Can you check, please?

[eskatos]

Hey @mantoni, thanks for the feedback.
Unfortunately, for various reasons, I switched to other tools for the concerned project so won't be able to check.