MockHttp is a testing layer for Microsoft's HttpClient library. It allows stubbed responses to be configured for matched HTTP requests and can be used to test your application's service layer. 

var mockHttp = new MockHttpMessageHandler();

// Setup a respond for the user api (including a wildcard in the URL)
mockHttp.When("http://localhost/api/user/*")
        .Respond("application/json", "{'name' : 'Test McGee'}"); // Respond with JSON

// Inject the handler or client into your application code
var client = mockHttp.ToHttpClient();

var response = await client.GetAsync("http://localhost/api/user/1234");
// or without async: var response = client.GetAsync("http://localhost/api/user/1234").Result;

var json = await response.Content.ReadAsStringAsync();

// No network connection required
Console.Write(json); // {'name' : 'Test McGee'}

Install-Package Mongo2Go

using (var runner = MongoDbRunner.Start())
{
   var client = new MongoClient(runner.ConnectionString);
   var database = client.GetDatabase("IntegrationTest");
   var collection = database.GetCollection<TestDocument>("TestCollection");
   //Just use it!
}

SqlInMemory is a library for creating SqlServer database on Memory instead of hard disk, at last Drops and Disposes database when you're done with it.

 This is useful for Integration Testing. 

This is a list of Automated Testing Frameworks for .NET related to methodologies and types of tests:

• Test-Driven Development (TDD)
• Behavior-Driven Development (BDD)
• Specification by Example (SBE)
• Acceptance Test-Driven Development (ATDD)
• Property-Based Testing (PBT)
• Unit \ Integration \ Acceptance \ Specification \ etc. Tests 

Software Testing Anti-Pattern List
- Having unit tests without integration tests
- Having integration tests without unit tests
- Having the wrong kind of tests
- Testing the wrong functionality
- Testing internal implementation
- Paying excessive attention to test coverage
- Having flaky or slow tests
- Running tests manually
- Treating test code as a second class citizen
- Not converting production bugs to tests
- Treating TDD as a religion
- Writing tests without reading documentation first
- Giving testing a bad reputation out of ignorance