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 am using expresso 0.9.2 and whenever a test is failing I am seeing the following error on each test case that is failing:
uncaught undefined: TypeError: Object # has no method 'callback'
at IncomingMessage. (/usr/local/lib/node_modules/expresso/bin/expresso:525:26)
at IncomingMessage.emit (events.js:81:20)
at HTTPParser.onMessageComplete (http.js:133:23)
at Socket.ondata (http.js:1231:22)
at Socket._onReadable (net.js:677:27)
at IOWatcher.onReadable as callback
TypeError: Object # has no method 'callback'
at IncomingMessage. (/usr/local/lib/node_modules/expresso/bin/expresso:525:26)
at IncomingMessage.emit (events.js:81:20)
at HTTPParser.onMessageComplete (http.js:133:23)
at Socket.ondata (http.js:1231:22)
at Socket._onReadable (net.js:677:27)
at IOWatcher.onReadable as callback
This makes it harder to actually see the stacktrace from the failing test. I can workaround this issue by adding a method "callback" from within my test, but I am not sure whats the purpose of this callback is.
The text was updated successfully, but these errors were encountered:
Same problem here. As bpasero said, set callback to avoid the problem:
exports.testHelloWorld = function(beforeExit, assert) {
this.callback = function(){};
...
}
I am using expresso 0.9.2 and whenever a test is failing I am seeing the following error on each test case that is failing:
uncaught undefined: TypeError: Object # has no method 'callback'
at IncomingMessage. (/usr/local/lib/node_modules/expresso/bin/expresso:525:26)
at IncomingMessage.emit (events.js:81:20)
at HTTPParser.onMessageComplete (http.js:133:23)
at Socket.ondata (http.js:1231:22)
at Socket._onReadable (net.js:677:27)
at IOWatcher.onReadable as callback
TypeError: Object # has no method 'callback'
at IncomingMessage. (/usr/local/lib/node_modules/expresso/bin/expresso:525:26)
at IncomingMessage.emit (events.js:81:20)
at HTTPParser.onMessageComplete (http.js:133:23)
at Socket.ondata (http.js:1231:22)
at Socket._onReadable (net.js:677:27)
at IOWatcher.onReadable as callback
This makes it harder to actually see the stacktrace from the failing test. I can workaround this issue by adding a method "callback" from within my test, but I am not sure whats the purpose of this callback is.
The text was updated successfully, but these errors were encountered: