Chai-As-Promised is eating assertion errors

[domenic]

Chai-As-Promised is eating assertion errors

[domenic]

Can you produce a small JavaScript file (not CoffeeScript) that demonstrates the problem, with as few external dependencies as possible? E.g. if you can demonstrate the problem without requiring me to install Selenium that would be much better and add much less friction to allowing me to fix this.

[kumarharsh]

Will do that, although it may take some time. I tried the normal promise-based chai test (using Q's deferred), and it works perfectly. I'll try to make a reproducible case. I have a doubt if it's something to do with mixing the webdriver and Q promises...

[kumarharsh]

Meanwhile, here is a gist of what I've been able to track down using the same tests (involving webdriver)

https://gist.github.com/kumarharsh/8279594

I've tried to make things clearer with comments. Hope it helps a little.

[tombatossals]

Hi, I'm using AngularJS protractor (webdriver wrapper) with cucumberJS and chai and chai-as-promised, and I'm getting a similar problem.

The chains seems to work fine but on some situations with the webdriver promises the expectation resolves as valid when it had to be false.

Will try to make a simple example demonstrating this behaviour.

[domenic]

As with #42 this appears to be a problem with third-party libraries, as nobody was able to produce a repro without a third-party library involved. My guess is that the library under use (webdriver?) does not produce Promises/A+ compliant promises; you should open an issue with them.

If someone can produce an example showing Chai as Promised to be at fault, without having to install a third-party library like webdriver, I'm happy to reopen.

[johnelm]

@domenic I'm just getting started with chai-as-promised for my WebDriverJS project. @kumarharsh where did you land with this? Did you have to stop using chai-as-promised for your webdriver stuff?