Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Log4net does not throw exceptions: <a href="http://logging.apache.org/log4net/release/faq.html" rel="noreferrer">http://logging.apache.org/log4net/release/faq.html</a></p> <p>Writing to an log on disk or in a database in a unit test is counterproductive; the whole point is automation. You shouldn't have to check the logs every time you run tests.</p> <p>If you truly need to verify that a call was made to log something, you should mock the <code>ILog</code> interface and assert that the appropriate method was called.</p> <p>If you are using a mocking framework, this is trivial. If you aren't, you can create a <code>TestLogger</code> class that implements or partially implements <code>ILog</code> and exposes extra properties that show how many times a given method was called. Your assertions will check that the methods were called as expected.</p> <p>Here is an example of a class to be tested:</p> <pre><code> public class MyComponent { private readonly ILog _log; public MyComponent(ILog log) { _log = log; } public string DoSomething(int arg) { _log.InfoFormat("Argument was [{0}]", arg); return arg.ToString(); } } </code></pre> <p>and the test (using Rhino.Mocks to mock the ILog):</p> <pre><code>[TestClass] public class MyComponentTests { [TestMethod] public void DoSomethingTest() { var logger = MockRepository.GenerateStub&lt;ILog&gt;(); var component = new MyComponent(logger); var result = component.DoSomething(8); Assert.AreEqual("8", result); logger.AssertWasCalled(l =&gt; l.InfoFormat(Arg&lt;string&gt;.Is.Anything, Arg&lt;int&gt;.Is.Equal(8))); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUnit Test & Log4net
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJay
    1. USJay
    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. COUnless the purpose of the application is to produce a log, writing a unit test to validate logging has occurred is merely leaking implementation details into the test. Test behavior, not implementation.
      singulars
      1. PO
      1. USbryanbcook
    2. CO@bryanbcook Are you agreeing or disagreeing with the answer?
      singulars
      1. PO
      1. USJay
    3. COI guess I'm more concerned with the question as I wouldn't want to promote writing unit tests that validate logging has occurred.
      singulars
      1. PO
      1. USbryanbcook
 

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