Hi Steve,

Thanks for posting! It's great to hear your team is getting on board with NCrunch, and I'm sure we can solve this issue quickly.

I strongly suspect that this issue is being caused by state/sequence dependent behaviour between the tests being executed. Most test runners will execute tests in order of A-Z, although NCrunch will execute tests in order of their priority. If you haven't already, make sure you have a read of the test atomicity considerations in the documentation. The troubleshooting test issues page may also contain a few useful tips.

Because DateTime parsing is culture-specific, I wonder if perhaps you may have a test somewhere in the codebase that changes the current culture on the testing thread. Note that changing the culture in a test WILL cause the culture to be changed for subsequently executed tests unless the previous culture is properly restored. It may be worth searching through your codebase for anything that changes the current culture.

Are you able to share any more details about the error you're seeing from your code?


Cheers,

Remco