Closed Bartvds closed 11 years ago
Thank you! I've already got a feeling I know what's the culprit here — I was naïvely asserting the stack trace had forward slashes for file paths.
I'll fire a VM up to make sure, but I'll bet if you replace /
with \
in assertions_test.js#L25 the tests will pass.
Just adding that this should affect tests only, not the functioning of the library itself.
Likely, but how do you know? Does the test pass? :smile:
Well, to be perfectly pedantic, I had a feeling I know. I might not really know, but the feeling is there! :-P I'll give the VM a try in the morning, but would you mind testing that feeling out? :)
Sure, commit some and I can run it and tweak a bit if needed.
Oh, I just thought if you could try the fix yourself, but here's the fixed line that I had in mind:
assert(stack[1].match(/[\/\\]test[\/\\]/), "must have test at top")
Closed per #2
Thanks again! I just published v0.1.338 to NPM with this fix, too.
Using the global
mocha
1.13.0 on Windows on Node 10.17.0If it is a Windows issue I might look into it later (need to do other stuff)
FYI: If you need a Windows VM: they are free here: http://www.modern.ie/en-us/virtualization-tools#downloads (Vagrant/Chef for Windows isn't there yet)