Ability to Mock Multiple Dapper Calls at a Time about moq.dapper HOT 11 OPEN

        [Test]
        public void Callback()
        {
            var connection = new Mock<IDbConnection>();

            int[] firstExpected = { 15 };
            int[] secondExpected = { 20 };

            IEnumerable<int> expected = firstExpected;

            connection.SetupDapper(x => x.Query<int>(It.IsAny<string>(), null, null, true, null, null))
                      .Returns(() => expected)
                      .Callback(() => expected = secondExpected);

            var firstActual = connection.Object.Query<int>("");
            Assert.That(firstActual, Is.EquivalentTo(firstExpected));

            var secondActual = connection.Object.Query<int>("");
            Assert.That(secondActual, Is.EquivalentTo(secondExpected));
        }

this may work as a solution. getting it to work appears to be way more complicated than I thought; it's hard to get the previous return value from Moq even with reflection and the ugly alternative is to keep a dictionary of the mocks and return values. I'm going for the hack, but new problems are bubbling up

from moq.dapper.

Hi @steventmayer, I may have some time in December to look at this, from a first glance at the specs, I would check the behaviour of Moq in this case, I have a feeling that it overrides the previous setup, too. One way to get around this would be to add a SetupSequence which I think may be not so difficult to implement and you would be able to setup multiple objects to return.

from moq.dapper.

Let me try playing around with SetupSequence . One area I was looking at was the ability to limit it if I declared the SQL ( c.QueryAsync("SP.StoredProcName" above instead) but need to look further into expressions. If I'm able to get something working, I'll put a PR in and see if you're interested.

from moq.dapper.

Thanks, I'll do my best to find some time to look at the PR as soon as possible.

from moq.dapper.

Let me try playing around with SetupSequence . One area I was looking at was the ability to limit it if I declared the SQL ( c.QueryAsync("SP.StoredProcName" above instead) but need to look further into expressions. If I'm able to get something working, I'll put a PR in and see if you're interested.

@steventmayer

Do you mind if I ask for a simple sample?

from moq.dapper.

@steventmayer @UnoSD @shahabganji

Did this get resolved?

from moq.dapper.

@steventmayer @UnoSD would like an update on the status of this if possible.

Thanks

from moq.dapper.

Is there a solution to this yet?

from moq.dapper.

Is there a solution to this yet?

I haven't ran into one myself and our unfortunate result so far is omitting the functions from code coverage.

Looks as if this repo is finished as the owner hasn't been active here or on GitHub in a long time.

from moq.dapper.

Is there any update on this issue please?
This hack is not working for me @UnoSD

        _mockIDbConnection
           .SetupDapperAsync(c => c.QueryAsync<ComboDishListModel>(
               It.IsAny<string>(), // You can specify the exact SQL query if needed
               It.IsAny<object>(),  // You can specify the expected parameters if needed
               It.IsAny<IDbTransaction>(),
               It.IsAny<int?>(),
               It.IsAny<CommandType?>()))
           .ReturnsAsync(comboDishListModels); // Provide the expected result

        _mockIDbConnection
.SetupDapperAsync(c => c.QueryAsync<OrderViewModel>(
    It.IsAny<string>(),
    new { command.OrderId, command.UserId },
    It.IsAny<IDbTransaction>(),
    It.IsAny<int?>(),
    It.IsAny<CommandType?>()))
.ReturnsAsync(ordersResult);

When apply the second setup, it overrides the first mock setup, even if T is different

from moq.dapper.

@yogeshk97 at the moment I do not have the capacity for working on the repo, but I welcome PRs and I am happy to review.

from moq.dapper.