Weird exception during integration tests #438
-
Hi @drewburlingame
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hi @KrzM , That sounds like an annoying problem. Given the error message, I do not have nearly enough information to help you troubleshoot and it could be due to a number of different things. Too many for me to throw out wild guesses. I am confident this is not caused by a bug CommandDotNet. We have hundreds of tests creating instances of the same app and haven't encountered this. I've also not encountered it in any other apps I've created with the framework. I'd suggest either debugging all the tests or adding log statements every time pop is called along with the object id to understand what may be using the same instance and working backward from there. |
Beta Was this translation helpful? Give feedback.
Hi @KrzM ,
That sounds like an annoying problem. Given the error message, I do not have nearly enough information to help you troubleshoot and it could be due to a number of different things. Too many for me to throw out wild guesses. I am confident this is not caused by a bug CommandDotNet. We have hundreds of tests creating instances of the same app and haven't encountered this. I've also not encountered it in any other apps I've created with the framework.
I'd suggest either debugging all the tests or adding log statements every time pop is called along with the object id to understand what may be using the same instance and working backward from there.