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'm not sure what is causing my issue, if its when or maybe Jasmine. But here is my problem (there is this repo for it). When trying to resolve a promise in a test its not working in a more or less specific use case, if I do the same w/o Jasmine its working totally fine.
So here is what it does:
var when = require('when');
var agg = require('./aggregate');
var a = agg(() => {
return when.promise((resolve) => {
resolve();
});
});
a().done(() => {
console.log('where are done, yeah');
});
The handler inside agg(...) will be called only every x times, for the test its actually every single call. If this handler is resolved, the handler attached to the promise of the a() call should be fired. But unfortunately its only working outside the scope of a test. For testing purpose the docker compose can be used by running docker-compose run test-6 or docker-compose run working-6
Did someone have similar issues and already resolved them?
Best
Andreas
The text was updated successfully, but these errors were encountered:
Hi everyone,
I'm not sure what is causing my issue, if its when or maybe Jasmine. But here is my problem (there is this repo for it). When trying to resolve a promise in a test its not working in a more or less specific use case, if I do the same w/o Jasmine its working totally fine.
So here is what it does:
The handler inside
agg(...)
will be called only every x times, for the test its actually every single call. If this handler is resolved, the handler attached to the promise of thea()
call should be fired. But unfortunately its only working outside the scope of a test. For testing purpose the docker compose can be used by runningdocker-compose run test-6
ordocker-compose run working-6
Did someone have similar issues and already resolved them?
Best
Andreas
The text was updated successfully, but these errors were encountered: