You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using chai-as-promised to do some chaining like this:
browser.init({browserName:'chrome'}).get("http://admc.io/wd/test-pages/guinea-pig.html").title().should.become('I am a page title - Sauce Labs').elementById('i am a link').click().eval("window.location.href").should.eventually.include('guinea-pig2').fin(function(){returnbrowser.quit();}).done();
It was working fine before 4.0, cause the input and output promise were the same, but now the chain broken cause all there is is a then method.
Now I understand why the 4.0 rewrite is simpler, but it would be good to be able to enrich the output. For example if you are using Q promise, and you cannot do something like this, it does not feel right.
var promise = Q.fcall(function() {return "1234";});
promise.should.become('1234').done();
The text was updated successfully, but these errors were encountered:
I was using chai-as-promised to do some chaining like this:
(see wd project)
It was working fine before 4.0, cause the input and output promise were the same, but now the chain broken cause all there is is a
then
method.Now I understand why the 4.0 rewrite is simpler, but it would be good to be able to enrich the output. For example if you are using Q promise, and you cannot do something like this, it does not feel right.
The text was updated successfully, but these errors were encountered: