fix: failure message when using Within

[vbreuss]

This PR improves the failure output when Mockolate verifications are used with Within(...) by ensuring timeouts produce aweXpect failure messages that include a useful “Interactions” context, and adds regression tests for the expected messages.

Key Changes:

• Catch MockVerificationTimeoutException during async verification to convert timeouts into aweXpect constraint failures and attach interactions context.
• Add new test cases asserting descriptive failure messages for Within(...) across multiple count-based constraints.
• Update Mockolate package reference from 2.0.0-pre.7 to 2.0.0.

---

• Fixes the last issue from Prepare for 2.0 release #78

[github-actions]

Test Results

    8 files  ± 0      8 suites  ±0   50s ⏱️ +4s
  197 tests + 8    196 ✅ + 8  1 💤 ±0  0 ❌ ±0 
1 312 runs  +56  1 311 ✅ +56  1 💤 ±0  0 ❌ ±0 

Results for commit 42d2ff0. ± Comparison against base commit 730514d.

♻️ This comment has been updated with latest results.

[github-actions]

🚀 Benchmark Results

Details

BenchmarkDotNet v0.15.8, Linux Ubuntu 24.04.3 LTS (Noble Numbat)

AMD EPYC 7763 2.45GHz, 1 CPU, 4 logical and 2 physical cores

.NET SDK 10.0.201

[Host]     : .NET 10.0.5 (10.0.5, 10.0.526.15411), X64 RyuJIT x86-64-v3

DefaultJob : .NET 10.0.5 (10.0.5, 10.0.526.15411), X64 RyuJIT x86-64-v3

Method	Mean	Error	StdDev	Median	Allocated
Dummy_aweXpect	0.0002 ns	0.0005 ns	0.0005 ns	0.0 ns	-

[Copilot]

Pull request overview

This PR improves the failure output when Mockolate verifications are used with Within(...) by ensuring timeouts produce aweXpect failure messages that include a useful “Interactions” context, and adds regression tests for the expected messages.

Changes:

• Catch MockVerificationTimeoutException during async verification to convert timeouts into aweXpect constraint failures and attach interactions context.
• Add new test cases asserting descriptive failure messages for Within(...) across multiple count-based constraints.
• Update Mockolate package reference from 2.0.0-pre.7 to 2.0.0.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.TwiceTests.cs	Adds regression test for Twice().Within(...) timeout message content.
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.TimesTests.cs	Adds regression test for Times(predicate).Within(...) timeout message content.
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.OnceTests.cs	Adds regression test for Once().Within(...) timeout message content.
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.ExactlyTests.cs	Adds regression test for Exactly(...).Within(...) and imports aweXpect.Core for n.Times().
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.BetweenTests.cs	Adds regression test for Between(...).And(...).Within(...) and imports aweXpect.Core for n.Times().
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.AtLeastTwiceTests.cs	Adds regression test for AtLeastTwice().Within(...) timeout message content.
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.AtLeastTests.cs	Adds regression test for AtLeast(n).Within(...) timeout message content.
Tests/aweXpect.Mockolate.Tests/ThatVerificationResultIs.AtLeastOnceTests.cs	Adds regression test for AtLeastOnce().Within(...) timeout message content.
Source/aweXpect.Mockolate/ThatVerificationResult.cs	Converts async timeout exceptions into constraint failures and ensures “Interactions” context is set/updated.
Source/aweXpect.Mockolate/ThatVerificationResult.Times.cs	Same timeout-to-failure handling for predicate-based Times(...) verification.
Source/aweXpect.Mockolate/ThatVerificationResult.Between.cs	Same timeout-to-failure handling for Between(...).And(...) verification.
Directory.Packages.props	Bumps Mockolate dependency to 2.0.0.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

This is addressed in release v2.0.0.