You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read lots of posts about not creating multiple Ninject kernels in a single process. We have avoided doing that even in tests. However, it appears that vstest.console.exe and Visual Studio when running [TestClass] tagged MSTest classes are running them all in the same process. Not even in separate AppDomain(s). So my tests fail when run together, and pass when run individually. So several questions. Is there a way to completely clean up all Ninject kernels in perhaps the [ClassCleanup] tagged method, so that it does not mess with the next test? Is there a technique to run multiple MSTest(s) with Ninject, such as a custom TestAdapter that implements ITestExecutor? As a sanity check, should you be able to normally run multiple MSTest(s) with Ninject kernels, and another issue is causing the tests to fail? Thank you.
The text was updated successfully, but these errors were encountered:
I have read lots of posts about not creating multiple Ninject kernels in a single process. We have avoided doing that even in tests. However, it appears that vstest.console.exe and Visual Studio when running [TestClass] tagged MSTest classes are running them all in the same process. Not even in separate AppDomain(s). So my tests fail when run together, and pass when run individually. So several questions. Is there a way to completely clean up all Ninject kernels in perhaps the [ClassCleanup] tagged method, so that it does not mess with the next test? Is there a technique to run multiple MSTest(s) with Ninject, such as a custom TestAdapter that implements ITestExecutor? As a sanity check, should you be able to normally run multiple MSTest(s) with Ninject kernels, and another issue is causing the tests to fail? Thank you.
The text was updated successfully, but these errors were encountered: