Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First, you can avoid the conflict between <code>Moq</code> and <code>MSpec</code> by declaring</p> <pre><code>using Machine.Specifications; using Moq; using It = Machine.Specifications.It; </code></pre> <p>Then you'll only need to prefix with <code>Moq.</code> when you want to use Moq's <code>It</code>, for example <code>Moq.It.IsAny&lt;&gt;()</code>.</p> <hr> <p><strong>Onto your question.</strong></p> <p><em>Note: This is not the original answer but an edited one after the OP added some real example code to the question</em></p> <p>I've been trying out your sample code and I think it's got more to do with MSpec than Moq. Apparently (and I didn't know this either), when you modify the state of your SUT (System Under Test) inside an <code>It</code> delegate the changes gets remembered. What is happening now is:</p> <ol> <li><code>Because</code> delegate is run</li> <li><code>It</code> delegates are run, one after the other. If one changes the state, the following <code>It</code> <em>will never see the set up in the</em> <code>Because</code>. Hence your failed test.</li> </ol> <p>I've tried marking your spec with the <code>SetupForEachSpecificationAttribute</code>:</p> <pre><code>[Subject(typeof(object)), SetupForEachSpecification] public class When_Testing { // Something, Something, something... } </code></pre> <p>The attribute does as its name says: It will run your <code>Establish</code> and <code>Because</code> <em>before every</em> <code>It</code>. Adding the attribute made the spec behave as expected: 3 Successes, one fail (the verification that with Var = "two").</p> <p>Would the <code>SetupForEachSpecificationAttribute</code> solve your problem or is resetting after every <code>It</code> not acceptable for your tests?</p> <p>FYI: I'm using <code>Moq v4.0.10827.0</code> and <code>MSpec v0.4.9.0</code></p> <hr> <p>Free tip #2: If you're testing ASP.NET MVC apps with Mspec you might want to take a look at <a href="http://jamesbroo.me/introducing-machinespecificationsmvc/" rel="nofollow">James Broome's MSpec extensions for MVC</a></p>
    singulars
    1. This table or related slice is empty.
    1. POUnexpected Validate behavior with Moq
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSergi Papaseit
    1. USSergi Papaseit
    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. This table or related slice is empty.
    1. COI think you may have misinterpreted my example. I only provided the MSpec code as something that could easily be run to display the same results that I am seeing in normal tests. Just so you are aware, I do use the Establish delegate, generally in an abstract class, but did not see the need for this example. I understand the purpose of the 'It' delegate, but in my experience it can be used to set variables. I will try to add some actual code for clarification, but it would not be able to be run. I appreciate your tip on the 'It' conflict. I will definitely use that in future.
      singulars
      1. PO
      1. USAwesomeYetIronicPseudonym
    2. CO@AwesomeYetIronicPseudonym - Ah, I see. See if you can indeed add some actual code and I'll try and give it another go :)
      singulars
      1. PO
      1. USSergi Papaseit
    3. COSergi, I've added in the additional code. Please let me know if it clarifies things a bit.
      singulars
      1. PO
      1. USAwesomeYetIronicPseudonym
 

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