Fix for Equality check on floating point values

[samsmithnz]

To fix the issue, the code should avoid comparing floating-point values for equality using ==. Since System.Math.Round(result, 0) is meant to convert the floating-point result to the nearest whole number, it is better to either:

1. Compare integer values directly (i.e., cast the rounded value to an integer before comparing); or
2. Use a tolerance to check if the value is "close enough" to the expected value.

Since the test is logically intended to check that, after rounding, the number of M&Ms matches the expected integer, the most robust approach is to cast the rounded result to an integer and then compare it to the integer value 45. To make the code clearer, both values being compared should be integers.

Specifically, on line 71, replace:

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

with:

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

This both simplifies the test assertion (using AreEqual rather than IsTrue), and compares integer values, removing reliance on floating-point equality.

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

[samsmithnz]

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

[Copilot]

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

[github-actions]

Pull Request Test Coverage Report for Build 19940168901

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 19939713209:	0.0%
Covered Lines:	100
Relevant Lines:	101

---

💛 - Coveralls