implemented API for set dbconnection

[unby]

Hi @rgvlee
Implemented a feature to set a specific DbConnection.
It allows testing dapper extensions with mock connection

[rgvlee]

Hi @unby, thanks for the contribution, it's much appreciated.

What is the use case here? Using EFCore and Dapper at the same time? (not an arrangement that I've used before). I'd have thought it'd one or the other in most cases. Can you elaborate on the use case/s?

Was it intentional that you've modified the EFCore 5 branch? Or should this be targeting EFCore 6?

[unby]

I want to use native API which can me get a lot of control

1. Output parameters when I work with legacy code
2. Multiple results when I optimize SQL query
3. And there are other reasons when we work with Context.Database.GetDbConnection() directly

It does not have to be only Dapper

I modified EFCore 5 branch because I tested the feature on my job project. I am ready to merge to EFCore 6 branch after code review

[rgvlee]

Thanks, so it seems that provided Context.Database.GetDbConnection() returns something, it'd satisfy the use case?

Do you find you have to do further set up on the mocked DbConnection? Or just having an object rather than null suffices.

There may be several approaches to support the use case.

[unby]

I want to emulate the database behind via DbConnection. I need to configure mock DbConnection

[unby]

@rgvlee, what do you think about the feature?

[rgvlee]

I'm open to a change to the mock, but cautious about a change to the mock builder.

The library provides functionality to extend the mock for supported relational operations. What we're saying here is that we're providing support for a mock db connection, but pushing any set up back on to the user rather than via the library. That in itself isn't a deal breaker, but how we deliver that needs to be considered.

As this isn't a case that I have used personally, I'd like to try the use cases and assess what the MVP state of the db connection needs to be. From there I'll make a decision about whether we modify the mock itself, or the mock and the mock builder.

[unby]

I prepared full sample for continetue discussion
https://github.com/unby/EntityFrameworkCore.Testing/blob/dbConnection_case/src/EntityFrameworkCore.Testing.Moq.Tests/FullCaseSample.cs#L26

[unby]

Hi @rgvlee, can I prepare PR for 4.x brunch?

[rgvlee]

I'm working my way through some bugfixes and enhancements, this is on my list of things to look into. Hold off on updating another branch just yet.