title: Visual Studio Unit Test: why test run inconclusive whereas testing same float values?
body: <p>I'm learning VS Unit test and tried this:</p>
  <pre><code>    [TestMethod()]
      public void calcTest()
      {
          double expected = 1.234F; // TODO: Initialize to an appropriate value
          double actual;
          actual = 1.234F;
          Assert.AreEqual(expected, actual);
          Assert.Inconclusive(&quot;Verify the correctness of this test method.&quot;);
      }
  </code></pre>
  <p>When running this test method, it says inconclusive ??? Why ?</p>
  <p>Update: Ok to tell don't compare floats, but business requirements are what they are. So what should I do if I need to compare them?</p>
  <p>Do you mean it's impossible to test floating calculation without headache? Then if testing is such a headache in financial calculation isn't it better to not do testing at all?</p>
  <p>Seems like a huge bug or design flaw in vs test framework rather :) as it is said here
  <a href="http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.testtools.unittesting.assert.inconclusive%28VS.80%29.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.testtools.unittesting.assert.inconclusive%28VS.80%29.aspx</a></p>
  <p>Indicates that an assertion cannot be proven true or false.</p>
  <p>Since I compare 2 same litterals sure it is true.</p>