Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's how you can mock your <code>FileConnection</code></p> <pre><code>Mock&lt;IFileConnection&gt; fileConnection = new Mock&lt;IFileConnection&gt;( MockBehavior.Strict); fileConnection.Setup(item =&gt; item.Get(It.IsAny&lt;string&gt;,It.IsAny&lt;string&gt;)) .Throws(new IOException()); </code></pre> <p>Then instantiate your Transfer class and use the mock in your method call</p> <pre><code>Transfer transfer = new Transfer(); transfer.GetFile(fileConnection.Object, someRemoteFilename, someLocalFileName); </code></pre> <p><strong>Update:</strong></p> <p>First of all you have to mock your dependencies only, not the class you are testing(Transfer class in this case). Stating those dependencies in your constructor make it easy to see what services your class needs to work. It also makes it possible to replace them with fakes when you are writing your unit tests. At the moment it's impossible to replace those properties with fakes.</p> <p>Since you are setting those properties using another dependency, I would write it like this:</p> <pre><code>public class Transfer { public Transfer(IInternalConfig internalConfig) { source = internalConfig.GetFileConnection("source"); destination = internalConfig.GetFileConnection("destination"); } //you should consider making these private or protected fields public virtual IFileConnection source { get; set; } public virtual IFileConnection destination { get; set; } public virtual void GetFile(IFileConnection connection, string remoteFilename, string localFilename) { connection.Get(remoteFilename, localFilename); } public virtual void PutFile(IFileConnection connection, string localFilename, string remoteFilename) { connection.Get(remoteFilename, localFilename); } public virtual void TransferFiles(string sourceName, string destName) { var tempName = Path.GetTempFileName(); GetFile(source, sourceName, tempName); PutFile(destination, tempName, destName); } } </code></pre> <p>This way you can mock internalConfig and make it return IFileConnection mocks that does what you want.</p>
    singulars
    1. This table or related slice is empty.
    1. POMocking a method to throw an exception (moq), but otherwise act like the mocked object?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSteveC
    1. USUfuk Hacıoğulları
    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. COHmm. Not what I was expecting, and now I see I simplified my `Transfer` class too much. Can you look at the changes I made to the `Transfer` class? This resembles my code a bit more closely. The properties are exposed in the class, but I did that mainly so I could test the exception condition. Is what I was trying to do the wrong way?
      singulars
      1. PO
      1. USJeremy Holovacs
    2. CO@JeremyHolovacs I have updated my answer.
      singulars
      1. PO
      1. USUfuk Hacıoğulları
    3. COHmm. What I thought would be simple seems to be getting less so. Let me ask you this: would it make more sense to create a test class that inherits from `Transfer` and override the method for testing purposes? Perhaps mocking is not the proper technology to use in this scenario, and I'm trying to shove a square peg into a round hole?
      singulars
      1. PO
      1. USJeremy Holovacs
 

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