Databases
StackOverflow2013
Postsdbo
POKung foo invocations strike multiple times, how to know what called the method from a test?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POKung foo invocations strike multiple times, how to know what called the method from a test?
    primarykey
    data
    text
    <p>OK - so I have this test. I wrote it expecting it would fail because my OnSaveCommand does call my adapters Save method yet. But to my surprise it failed saying "Invocation was performed more than once on the mock". I am totally confused. I am not called it at all <em>goink</em>. My problem is I don't know how to tell what is called it? If I where running the code I would throw in a break point and just look at the call stack when it gets called but that doesn't really work here because it's a mock of course. </p> <p>I tried to look at the moq quickstart for some ideas but the truth is I am just stumped. The first part of the test publishes an event that causes the DiscountsForSelectedCompany list to get populated, I can see that all that happens, then I execute the save command right? Then I get the error. Like I said, I am stumped - if someone could point me in the right direction that would be awesome. </p> <pre><code>[Test] public void SaveCommand_Will_Call_Adapter_SaveDiscounts_For_All_Edited_Discounts() { eventAggregator.GetEvent&lt;SetCompanyIdEvent&gt;().Publish(182); vm.DiscountsForSelectedCompany.Single(x =&gt; x.Id == 1).IsEdited = true; mockVariablePricingAdapter.Setup(x =&gt; x.SaveDiscounts( It.Is&lt;List&lt;DisplayCompanyDiscount&gt;&gt;(a =&gt; a.First().Id == 1)) ).Verifiable(); vm.SaveCommand.Execute(); mockVariablePricingAdapter.Verify(x =&gt; x.SaveDiscounts(It.Is&lt;List&lt;DisplayCompanyDiscount&gt;&gt;(a =&gt; a.First().Id == 1)), Times.Once()); } </code></pre> <p>Thanks!</p> <p>EIDT! WHOO - HEY!!! I changed the "Times.Once()" to "Times.AtLeastOnec()" and sure enough if fails saying "Invocation was not performed on the mock:" - Does anyone know about this? Is it a bug? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKenn
    1. USKenn
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POKung foo invocations strike multiple times, how to know what called the method from a test?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POKung foo invocations strike multiple times, how to know what called the method from a test?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COyou had me at `Kung foo <something> strike multiple times` ;)
      singulars
      1. POKung foo invocations strike multiple times, how to know what called the method from a test?
      1. USJakub
    2. CODoes [Using MOQ to test non-primitive arguments](http://stackoverflow.com/questions/2245710/using-moq-to-test-methods-that-accept-non-primative-arguments) solve your issue?
      singulars
      1. POKung foo invocations strike multiple times, how to know what called the method from a test?
      1. USJoshua Drake
    3. COI changed it to Times.Exactly(1) which solves the issue and tests the behavior exactly as it should be.
      singulars
      1. POKung foo invocations strike multiple times, how to know what called the method from a test?
      1. USKenn
 

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