Add CheckEquality method to IEqualizer for boolean-based equality checks

[Copilot]

Pull Request Description

This PR introduces a new CheckEquality method to the IEqualizer interface, providing a boolean-based alternative to the existing exception-based AssertEquality and AssertInequality methods. This addresses use cases where a simple true/false result is preferred over exception-based flow control.

Motivation and Context

The IEqualizer interface previously only exposed AssertEquality and AssertInequality methods, which throw exceptions on assertion failure. However, there are common scenarios where developers need to check equality without the overhead of exception handling. The new CheckEquality method fills this gap by returning a boolean value (true if equal, false if not equal) without throwing exceptions.

Changes Made

• IEqualizer interface: Added CheckEquality(object? expected, object? actual) method signature with XML documentation
• Equalizer implementation: Implemented by delegating to the existing Equalize() internal method and returning the IsSuccessful property
• Test refactoring: Refactored existing tests to use helper methods (AssertEquality and AssertInequality) that internally validate both the new CheckEquality method and the original assertion methods, ensuring comprehensive coverage without adding redundant test cases

Usage Example

var equalizer = new Equalizer();

// Before: exception-based flow
try 
{
    equalizer.AssertEquality(expected, actual);
    // continue if equal
} 
catch (InvalidAssertException) 
{
    // handle inequality
}

// After: boolean-based flow
if (equalizer.CheckEquality(expected, actual)) 
{
    // continue if equal
} 
else 
{
    // handle inequality
}

The implementation reuses existing equalization logic without duplicating any comparison behavior. All existing tests now also validate that CheckEquality returns the correct boolean value, providing thorough test coverage.

Fixes #62

Checklist

• I have tested these changes thoroughly.
• I have added/updated relevant documentation.
• My code follows the project's coding guidelines.
• I have performed a self-review of my changes.
• My changes are backwards compatible.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Introduce the CheckEquality method</issue_title>
<issue_description>Describe your idea
Currently, the IEqualizer interface exposes only AssertEquality and AssertInequality methods. However, there are use cases in which we need the result as a boolean. I suggest we implement a new method - CheckEquality that will not throw exceptions for incorrect assertion, but will return true/false accordingly.

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Introduce the CheckEquality method #62

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[TonyTroeff]

The changes look great. I added two minor suggestions.

[TonyTroeff]

The changes look great. I added two minor suggestions.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: curl -I -sSL --retry 5 --retry-delay 2 --connect-timeout 15 REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud