> Thanks. Man, I miss VS right about now. I don't see anything obviously off, but *anytime* I've ever run across an issue where a test ran in isolation, but not many at once, one of two things was going on.
1. The test was inadvertently keeping global state (this one isn't).
2. A test was running a "fire and forget" asynchronous method.
I'm theorizing that something is being spun off into the background, but the test doesn't know to wait for it. I don't see anything that would be doing