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
Adding native support for promises in addition to the done() style callbacks for async before/after functions + tests would really improve the test writing/debugging experience for projects that depend on promises more so than node style callbacks. There are plenty of ways to make it work without native support, but nothing would beat it.
before/after functions:
In addition to signaling completion/failure of the before/after, it would be great if a promise returned from a before/after function that was rejected would cause the error passed to the reject handler to be logged to the console, and then fail every test in the immediate suite.
tests:
returning a promise from a test would simply signal test completion on resolution, or fail the test on rejection.
Has any of this been discussed or considered before?
The text was updated successfully, but these errors were encountered:
I'm seeing the same issues. Although done() should work in theory, it doesn't seem happy when used with the Bluebird promise library. Test execution just randomly stops mid-execution, but sometimes, for no apparent reason it works. Seems to be some kind of race condition going on.
Adding native support for promises in addition to the
done()
style callbacks for async before/after functions + tests would really improve the test writing/debugging experience for projects that depend on promises more so than node style callbacks. There are plenty of ways to make it work without native support, but nothing would beat it.before/after functions:
In addition to signaling completion/failure of the before/after, it would be great if a promise returned from a before/after function that was rejected would cause the error passed to the reject handler to be logged to the console, and then fail every test in the immediate suite.
tests:
returning a promise from a test would simply signal test completion on resolution, or fail the test on rejection.
Has any of this been discussed or considered before?
The text was updated successfully, but these errors were encountered: