I am reaching out to seek assistance regarding an execution order issue we have encountered when using the ReSharper Test Runner. In our C# project, we have implemented a comprehensive test suite that incorporates both unit and integration tests. To ensure proper data setup and deletion, we utilize the [ClassInitialize] attribute in some test classes to perform these tasks before any tests within the class are run. Additionally, for most test classes, we rely on the [TestInitialize] attribute to initialize the test-specific data. However, when running tests through the ReSharper Test Runner, the execution order is not respected. This leads to a critical problem where a test using the [TestInitialize] attribute can inadvertently delete the required data set up by the [ClassInitialize] method. Consequently, the test classes relying on [ClassInitialize] start to fail when subsequent tests run. This issue remains unnoticed when using the Visual Studio Test runner which respects the expected execution order. How can we resolve this execution order problem without having to rewrite many tests for the developers using R#? Is there any configuration or setting within ReSharper that can enforce the correct execution order of tests. Since this is a legacy project we are uncertain about the specific trigger that led to this problem. I have tried it with several older versions of R# but the problem remains.