Are there any good/best practices for dealing with floating point values when checking results with the fit framework?
Our application does many calculations. In most situations checking values a precision of more than 6 or 8 digits does not make any sense. So I would like to specify the precision that are used when comparing expected and actual values.
My brute force solution would be to set a precision value and then compare values in my ColumnFixture containing the test cases.
This would result in something like:
!|info.fitnesse.fixturegallery.ColumnFixtureTest| |firstSummand|secondSummand|precision|expectedResult|calculateSumAndCheck()| |2.1|3.3|0.0001|5.3|true|
The major drawback of this approach would be that I would not be able to use the compare features of fit but write my own ones.