This is useful when the application needs to create its own transaction but will fail since EF does not support cross-platform nested transactions.

This is useful when a shared change tracker gets in the way.

• Create test Startup class

• How to write custom fixtures that inherit from the base fixtures
• Avoid inheriting Startup. Underlying registrations may depend on the current assembly type. By inheriting, the return value of GetType().Assembly will become the test assembly rather than the application.
• Beware injections of scoped DbContext instances into singleton instances. You can enable debug logging to see which transaction ids are being used. If the same transaction is used for multiple tests, you probably have a registration scope issue. In this case, walk the registration tree upwards from the DbContext implementation, making sure all components are registered as scoped services.

Currently, if an exception occurs, the test will fail to rollback the operation. Need to see what is offered in xUnit that would allow us to wrap the tests.

• Assert.Equals with string message e.g.:

// act
var response = await _fixture.Client.GetAsync("/api/v1/articles");

// assert
var body = await response.Content.ReadAsStringAsync();
Assert.True(HttpStatusCode.OK == response.StatusCode, $"Received {response.StatusCode} status code with payload: {body}");

It seems this no longer works with .NET Core 3.0, possibly because they changed the way ConfigureServices() work. I have no clue how to get it working. Any chance of an update or some pointers?

Should provide the same abstractions as JsonServerFixture but use any startup desired

• No container dependency, services would have to be resolved from the application level service provider
• Maybe we can resolve the default scope provider and it will just work?
• Alternative for #3 ?