coverage: ensure that NaN is considered equal to NaN

[vbreuss]

No description provided.

[Copilot]

Pull Request Overview

This PR adds test coverage to ensure that NaN (Not a Number) values are correctly handled in the IsEqualTo().Within() assertion chain for floating-point numbers. The change addresses the mathematical edge case where NaN should be considered equal to itself when using tolerance-based comparisons.

• Adds comprehensive test coverage for NaN equality scenarios across all supported floating-point numeric types
• Tests both nullable and non-nullable variants of double and float types
• Validates that NaN == NaN evaluates to true within the assertion framework's tolerance-based comparison logic

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

Test Results

    10 files  ± 0      10 suites  ±0   4m 15s ⏱️ -19s
16 758 tests  -  1  16 757 ✅  -  1  1 💤 ±0  0 ❌ ±0 
47 028 runs  +12  47 027 ✅ +12  1 💤 ±0  0 ❌ ±0 

Results for commit 30eb0fb. ± Comparison against base commit 0b4a83e.

[github-actions]

This is addressed in release v2.27.0.