Switch from hard-coded fakes to a dynamic test isolation framework. about applicationinsights-aspnetcore HOT 8 CLOSED

My vote is for NSubstitute

from applicationinsights-aspnetcore.

We will start supporting dnxcore50 very soon. We need it to be supported by dynamic test isolation framework.

from applicationinsights-aspnetcore.

Do you suggest maintaining hand-written fakes until one of these frameworks supports dnxcore?

from applicationinsights-aspnetcore.

Yes. We cannot claim that we support a platform if we did not test it.

from applicationinsights-aspnetcore.

I don't think anyone is suggesting that we don't test on dnxcore. Whether or not we run unit tests on this platform is only a small part in supporting it. While I agree that it would be ideal to do so, we can choose to run the unit tests only on the full framework, while continuing to use functional and manual tests to verify that our code works on dnxcore.

from applicationinsights-aspnetcore.

I propose to close this issue until we have a fakes framework that supports core framework.

from applicationinsights-aspnetcore.

I found this one work with dnxcore50: http://nugot.net/package/LightMock.vNext

from applicationinsights-aspnetcore.

Looks interesting. Have you tried it? Does it work for you?

from applicationinsights-aspnetcore.