Unit testing is an integral part of modern software development. For years, Moq has been a popular choice in the .NET ecosystem for creating mock objects. Recent concerns over Moq’s SponsorLink feature have prompted some developers to consider such a switch. In this article, we delve into why you might consider NSubstitute over Moq and how to make the transition. 

1. Global query filters in Entity Framework Core 2.0
2. Implementing tenant providers on ASP.NET Core 
   
3. Implementing database per tenant strategy on ASP.NET Core
4. Handling missing tenants in ASP.NET Core
5. Unit testing multi-tenant database provider
6. Defensive database context for multi-tenant ASP.NET Core applications 

ReSharper 2018.3.2 bug-fix update fixes:

- Many issues in C#, VB.NET, and TypeScript Code Analysis.
- More than a dozen issues related to parameter name hints.
- Missing “Find Code Dependent on Module” item in a context menu for a project node in the Solution Explorer tab.
- Several issues in Unit Testing.
- Some issues related to auto-detect naming style.
 

• Add foreign key constraint checking to the in-memory provider
Reasoning: It is desirable for foreign keys to be validated when running unit tests. This allows bugs to be caught earlier without the need for integration testing against a real database.

• Transparency: عدم تغییر سیستم تحت آزمون: مثل افزودن امکانات اضافی به کد محصول جهت سهولت آزمایش
  
• Scope: قابلیت اجرا بر روی هر دو حالت Debug و Release
• Simplicity: سربار کم و سادگی تست برای تغییر