Fix for Equality check on floating point values

[samsmithnz]

To fix the problem, floating-point values should not be compared directly using ==. Instead, we should compare the absolute difference between the calculated value and the expected value against a small "epsilon" value, which defines the acceptable margin of error due to floating point imprecision.

Since the assertion is about a rounded number of M&Ms, and the expected value is an integer, we can either (1) compare integer values by casting the rounded value to an integer, or (2) define a small tolerance for float comparison (using something like Math.Abs(a - b) < epsilon). Using the integer comparison is simple and appropriate here since the value is rounded to zero decimals.

Therefore, in this file, change line 124 from:

Assert.IsTrue(System.Math.Round(result, 0) == 5f);

to:

Assert.AreEqual(5, (int)Math.Round(result, 0));

This will assert the rounded value equals 5 as an integer, which avoids all floating point equality issues.

Make similar changes on lines 96 and 110.

No new imports are needed, as Math is already in use.

---

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[github-actions]

Pull Request Test Coverage Report for Build 19939620337

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 81.992%

---

Totals
Change from base Build 19937062453:	0.0%
Covered Lines:	100
Relevant Lines:	101

---

💛 - Coveralls

[samsmithnz]

@copilot, make sure you fix this rule on all methods in this file.

[Copilot]

@samsmithnz I've opened a new pull request, #297, to work on those changes. Once the pull request is ready, I'll request review from you.