Closed christian-ciceri closed 10 years ago
Haven't used it with mocha, maybe if you show me a full working (failing) example I can help you.
Hi,
I cannot send you the example because it's confidential (it's a security context). I could try to reproduce it in a "fake project", when I have time. Nevertheless, it's quite simple. It's sufficient a little-sized project id TDD/BDD fashion, with a failing test in accessing a file (fs.readFile).
Thanks,
Christian
2014-09-23 3:02 GMT+02:00 Lucio M. Tato notifications@github.com:
Haven't used it with mocha, maybe if you show me a full working (failing) example I can help you.
— Reply to this email directly or view it on GitHub https://github.com/luciotato/waitfor/issues/23#issuecomment-56465550.
Hi,
the problem was mine: I forgot to put the call to the done method before closing the fiber scope. Sorry for creating an issue that wasn't related to your code. Anyway I hope that my experience with mocha and wait.for can help other users if they find themselves in the same situation.
Thank you very much,
Christian
2014-09-23 7:58 GMT+02:00 Christian Ciceri christian.ciceri@gmail.com:
Hi,
I cannot send you the example because it's confidential (it's a security context). I could try to reproduce it in a "fake project", when I have time. Nevertheless, it's quite simple. It's sufficient a little-sized project id TDD/BDD fashion, with a failing test in accessing a file (fs.readFile).
Thanks,
Christian
2014-09-23 3:02 GMT+02:00 Lucio M. Tato notifications@github.com:
Haven't used it with mocha, maybe if you show me a full working (failing) example I can help you.
— Reply to this email directly or view it on GitHub https://github.com/luciotato/waitfor/issues/23#issuecomment-56465550.
When I execute tests in which a launchFiber is specified, when the test fails, other unrelated tests fail as well. Which is the best strategy to use with mocha testing? Is it a bug of wait.for?