Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've been verifying calls in the same manner - I believe it is the right way to do it.</p> <pre><code>mockSomething.Verify(ms =&gt; ms.Method( It.IsAny&lt;int&gt;(), It.Is&lt;MyObject&gt;(mo =&gt; mo.Id == 5 &amp;&amp; mo.description == "test") ), Times.Once()); </code></pre> <p>If your lambda expression becomes unwieldy, you could create a function that takes <code>MyObject</code> as input and outputs <code>true</code>/<code>false</code>...</p> <pre><code>mockSomething.Verify(ms =&gt; ms.Method( It.IsAny&lt;int&gt;(), It.Is&lt;MyObject&gt;(mo =&gt; MyObjectFunc(mo)) ), Times.Once()); private bool MyObjectFunc(MyObject myObject) { return myObject.Id == 5 &amp;&amp; myObject.description == "test"; } </code></pre> <p>Also, be aware of a bug with Mock where the error message states that the method was called multiple times when it wasn't called at all. They might have fixed it by now - but if you see that message you might consider verifying that the method was actually called.</p> <p>EDIT: Here is an example of calling verify multiple times for those scenarios where you want to verify that you call a function for each object in a list (for example).</p> <pre><code>foreach (var item in myList) mockRepository.Verify(mr =&gt; mr.Update( It.Is&lt;MyObject&gt;(i =&gt; i.Id == item.Id &amp;&amp; i.LastUpdated == item.LastUpdated), Times.Once()); </code></pre> <p>Same approach for setup...</p> <pre><code>foreach (var item in myList) { var stuff = ... // some result specific to the item this.mockRepository .Setup(mr =&gt; mr.GetStuff(item.itemId)) .Returns(stuff); } </code></pre> <p>So each time GetStuff is called for that itemId, it will return stuff specific to that item. Alternatively, you could use a function that takes itemId as input and returns stuff.</p> <pre><code>this.mockRepository .Setup(mr =&gt; mr.GetStuff(It.IsAny&lt;int&gt;())) .Returns((int id) =&gt; SomeFunctionThatReturnsStuff(id)); </code></pre> <p>One other method I saw on a blog some time back (Phil Haack perhaps?) had setup returning from some kind of dequeue object - each time the function was called it would pull an item from a queue.</p>
    singulars
    1. This table or related slice is empty.
    1. POVerifying a specific parameter with Moq
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmanman
    1. USMayo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, it makes sense to me. What I still can't understand is when to specify details in Setup or Verify. It's quite confusing. At the moment, I'm just allowing anything in Setup and specifying the values in Verify.
      singulars
      1. PO
      1. USLuis Mirabal
    2. COHow do you think I can check the messages when there are multiple calls? The client take messages and can create multiple queueableMessages, which will end up in multiple calls and in each of those calls, I have to check different messages. I'm still struggling with unit testing in general, I'm not very familiar with it yet.
      singulars
      1. PO
      1. USLuis Mirabal
    3. COI don't think there's a magic silver bullet in terms of how you should do this. It takes practice and you start getting better. For me, I only specify parameters when I have something to compare them to and when I'm not already testing that parameter in another test. As for multiple calls there are several approaches. For setting up and verifying a function that is called multiple times, I usually call setup or verify (Times.Once()) for each call that I expect - often with a for loop. You can use the specific parameters to isolate each call.
      singulars
      1. PO
      1. USMayo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload