Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, Moq does <em>not</em> support mocking concrete classes. Only abstract classes and interfaces can be mocked. However, this is not as hard as it sounds. Let's take your log file handling as an example.</p> <p>Say you start with the following concrete logging class:</p> <pre><code>public class Log { public void WriteToLog(string message) { ... } } </code></pre> <p>We have another classes that uses this <code>Log</code> class to do its logging:</p> <pre><code>public class LogGenerator { public void Foo() { ... var log = new Log(); log.WriteToLog("my log message"); } } </code></pre> <p>The problem with unit testing the <code>Foo</code> method is that you have no control over the creation of the <code>Log</code> class. The first step is to apply <strong>inversion of control</strong>, where the caller gets to decide what instances are used:</p> <pre><code>public class LogGenerator { private readonly Log log; public LogGenerator(Log log) { this.log = log; } public void Foo() { ... this.log.WriteToLog("my log message"); } } </code></pre> <p>Now we are one step closer to successfully unit testing as our unit test can choose which <code>Log</code> instance to do the logging with. The last step now is to make the <code>Log</code> class mockable, which we could do by adding an interface <code>ILog</code> that is implemented by <code>Log</code> and have <code>LogGenerator</code> depend on that interface:</p> <pre><code>public interface ILog { void WriteToLog(string message); } public class Log : ILog { public void WriteToLog(string message) { ... } } public class LogGenerator { private readonly ILog log; public LogGenerator(ILog log) { this.log = log; } public void Foo() { ... this.log.WriteToLog("my log message"); } } </code></pre> <p>Now we can use Moq in our unit test to create a mock of an object implementing <code>ILog</code>:</p> <pre><code>public void FooLogsCorrectly() { // Arrange var logMock = new Mock&lt;ILog&gt;(); var logGenerator = new LogGenerator(logMock.Object); // Act logGenerator.Foo(); // Assert logMock.Verify(m =&gt; m.WriteToLog("my log message")); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMoq simple example required- database connection and file handling
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USErik Schierboom
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMoq simple example required- database connection and file handling
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. COMany thanks for the detialed explanation
      singulars
      1. PO
      1. USkarpanai
    2. CO"First of all, Moq does not support mocking concrete classes." - not true, it can. It just can't setup non-virtual properties/methods.
      singulars
      1. PO
      1. USSunny Milenov
 

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