# Unit testing floating point numbers

Testing for equality Floating point numbers is usually a bad idea, this because rounding occurs with floating point operations and you need to test with a tolerance. Suppose you test that some algorithm produces the expected result and you find that unit test fails with this message.

SharpTestsEx.AssertException : 2.36 Should Be Equal To 2.36.

This seems strange, but the problem is that the real value is 2.360000000003 that surely is different from 2.36. Now you have two different scenario, the first one is the test is wrong because I want to verify that the two numbers are really equals. With floating point calculation this cannot be achieved, you can use numbers with high precision, but doing operations with any floating point numbers lead to rounding, and you should never test for equality two floating point numbers.

A second and better scenario is when you the test is expressed with a tolerance, so you can write this assertion.

 ``````1 `````` ``````result.Should().Be.EqualTo(expectedresult, 0.00001) ``````

This is a better assertion, I’m asking if the result is different from the expected value with a 0.00001 tolerance. This is possible with a simple extension of SharpTestEx.

 `````` 1 2 3 4 5 6 7 8 9 10 `````` ``````public static IComparableBeConstraints EqualTo( this IComparableBeConstraints constraint, Double expected, Double tolerance) { constraint.AssertionInfo.AssertUsing( new Assertion( "Equal to", expected, a => Math.Abs(a - expected) <= tolerance)); return constraint; } ``````

Such test is much more interesting and correct, because it states the tolerance that you can suffer before stating that the algorithm is wrong.

Alk.