I think the problem is Blockchain.Singleton. We should try to remove Blockchain.Singleton and use dependency injection. Then all the tests are isolated.

@rodoufu #1042

I think the problem is with

I think it is correct to use this in TestInitialize, the problem is that this doesn't seem to create a new fresh Blockchain instance. Each call (and thus each test) should get a new clean instance. It's probably best to use the In-Memory blockchain if that's already merged somewhere, otherwise you'll probably have to add [TestCleanup].

I agree, @erikzhang, that DI could solve this in a more beautiful way.

However, even nowadays, it is possible to handle that. We should not have tests that are finishing with a modified status different than the original.

Thus, perhaps, until DI is not implemented we should fix the tests that are doing such behavior.

@rodoufu #1042

The DI may help to improve this kind of initialization for the tests.
But it may be also necessary to mock some stuff, probably we are going to register the components on the container differently for some tests.