-
Notifications
You must be signed in to change notification settings - Fork 52
Weird mocha behavior #63
Comments
I can help if you can show a commit where running the tests results in |
I've experience that also, and it can be seen in a Fuel-REST PR. (the subsequent failures are because that first one failed). The test is actually checking to see if a call is made twice, but it ends up being called 4 times, so that's wrong. I think it has to do with using a mocha version that doesn't support v0.8. Will likely look into that soon.
This is interesting. Test order shouldn't matter, but seems weird that it does. |
The latest version of mocha still supports Node.js 0.8 (it doesn't support 0.6 or lower, through). |
Hmm, then I have no clue why it would run them twice. Looks like I'll need to dig into it more |
not a problem anymore it seems as tests run on 0.8 consistently |
Very strange behavior observed with mocha. The order of the test files makes a difference. The issue is around function-soapRequest. I tried putting a new test in there after the 'describe' test but it always resulted in "Error: connect ECONNRESET" in the midst of reporting a test. Also, reporting indicated that certain tests were ran twice. Very strange stuff.
Prefixing a file with _ causes the file to be processed first. This worked for node 0.8x but caused it fail on 0.10x, or vice versa, I don't remember. Some of this may have been my mac. I ended up getting both 0.8 and 0.10 tests to work on another machine. But I had to call it "header-test" so it ran after the other tests.
The text was updated successfully, but these errors were encountered: