Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>When I use VS to generate the unit tests, I got Assert.Inclusive for generated test methods and usually I change the assertion so something else when I work them. I use the question marks of Assert.Inconclusive in test result as markers to quickly tell me which tests I have not yet completed.</p> <p>Well, it's just the way I use it. From its name "Inconclusive", I guess you can use to indicate your undeterministic state as long as you document what it means.</p> <p>However, from the description of your <code>Average()</code> method, I think that maybe your unit test is not atomic enough to cover just one "unit", one specific scenario. Sometimes, I write 2 or 3 unit test methods for a single method. Or you can break your <code>Average()</code> method to smaller methods covering single responsibilities. That way, you can unit test those smaller methods before unit testing you <code>Average()</code> one.</p> <hr> <p>Johannes,</p> <p>This is how I would implement the <code>Sum()</code> and <code>Average()</code> methods.</p> <pre><code>public static class MyMath { private static void ValidateInput(ICollection&lt;int&gt; numbers) { if (numbers == null) throw new ArgumentNullException("numbers", "Null input. Nothing to compute!"); if (numbers.Count == 0) throw new ArgumentException("Input is empty. Nothing to compute!"); } public static int Sum(int[] numbers) { ValidateInput(numbers); var total = 0; foreach (var number in numbers) total += number; return total; } public static double Average(int[] numbers) { ValidateInput(numbers); return Sum(numbers) / numbers.Length; } } </code></pre> <p>For simplicity, I just throw <code>ArgumentException</code> exceptions from the <code>ValidateInput(ICollection&lt;int&gt;)</code> method. You can also check for possibility to overflow and throw <code>OverflowException</code> in the <code>ValidateInput(ICollection&lt;int&gt;)</code> method.</p> <p>With that said, here's how I would test the <code>Average(int[])</code> function. </p> <pre><code>[TestMethod] public void AverageTest_GoodInput() { int[] numbers = {1, 2, 3}; const double expected = 2.0; var actual = MyMath.Average(numbers); Assert.AreEqual(expected, actual); } [TestMethod] [ExpectedException(typeof(ArgumentNullException))] public void AverageTest_NullInput() { int[] numbers = null; MyMath.Average(numbers); } [TestMethod] [ExpectedException(typeof(ArgumentException))] public void AverageTest_EmptyInput() { var numbers = new int[0]; MyMath.Average(numbers); } </code></pre> <p>With these tests setup, I can be certain that when all the tests pass, my function is correct. Well, except for the case of overflow. Now I can go back to the <code>ValidateInput(ICollection&lt;int&gt;)</code> method to add logic to check for overflow, then add one more test to expect the <code>OverflowException</code> to be thrown for the kind of inputs that cause overflow. Or doing it in the opposite order if you like to approach using TDD.</p> <p>I hope this helps clarify the idea.</p>
    singulars
    1. This table or related slice is empty.
    1. POUsage of Assert.Inconclusive
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UStranmq
    1. UStranmq
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsage of Assert.Inconclusive
      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. VTAcceptedByOriginator
    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. COcould you please elaborate how you would approach this in this very special case
      singulars
      1. PO
      1. USJohannes Rudolph
    2. COthank you very much. so in essence you are saying that there is no need to write an explicit test for Sum(), but testing it via Average(). From code coverage perspective this generates the same result anyway.
      singulars
      1. PO
      1. USJohannes Rudolph
    3. COI would also write tests for Sum(). Who knows in my sleepy moment, I might type the '-' instead of the '/'. :) With the tests for Sum() in place, if I got all the tests for Sum() pass but some test for Average() fail, I can be very certain that the implementation for Average() is wrong. I won't be able to blame Sum() for causing Average() to be wrong. :)
      singulars
      1. PO
      1. UStranmq
 

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