expect() might be redundant?

[caolan]

expect() might be redundant?

[caolan]

expect() doesn't exit as soon as the expected number of assertions have run, but rather checks that the completed number of assertions on test.done matches what you expect. This is to help detect callbacks firing multiple times or not at all.

From your code example it looks like you want to exit as soon as a specific number of assertions have been run. The problem with this is that you have no idea whether extra calls are being made to the callbacks, or which assertions have fired. It could be that your first assertion has fired 10 times by mistake, but passed each time.

[philjackson]

I need to do this because I found that, for a particularly well nested (and heavy) callback, nodeunit would print the results 'early' and assume a couple of tests hadn't run when actually they were running but just taking a while.

I suppose what I'm trying to achieve is done() blocking until at least the expected count has been met. Is there a common idiom for dealing with this scenario?

edit: "isnt" sould be "<" in the code.

[philjackson]

Oh, also, you would call superdone in the same place you might done() - so would still catch too many test runs.