[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
BenchmarkDotNet	nuget	patch	0.15.3 -> 0.15.4

---

Release Notes

dotnet/BenchmarkDotNet (BenchmarkDotNet)

v0.15.4: 0.15.4

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.4.html

Highlights

Allow override method/property for ParamsSource (#​2832)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: BenchmarkDotNet 0.15.3 → 0.15.4 Update ✅

Todo List:

• Examine the changed file (Directory.Packages.props)
• Review BenchmarkDotNet usage in the codebase
• Analyze potential impact on TUnit's benchmarks
• Check for security or breaking changes in 0.15.4
• Provide comprehensive review feedback

---

✅ Overall Assessment: APPROVE

This is a low-risk patch update that should be safe to merge. The dependency update only affects development/benchmarking tooling and doesn't impact TUnit's runtime or production code.

📋 Review Feedback

Code Quality & Best Practices ✅

• Clean change: Single line update in centralized package management (Directory.Packages.props:10)
• Proper versioning: Uses centralized package management correctly
• Consistent pattern: Follows established dependency update patterns

Potential Issues ⚠️

Minor Version Inconsistency:

• BenchmarkDotNet updated to 0.15.4 (✅)
• BenchmarkDotNet.Annotations remains at 0.15.3 (Directory.Packages.props:11)

Recommendation: Consider updating BenchmarkDotNet.Annotations to 0.15.4 in a follow-up for consistency, though this won't cause runtime issues.

Security Concerns ✅

• No security risks: BenchmarkDotNet is used only in test/benchmark projects
• Limited scope: Only affects performance testing infrastructure
• Trusted source: Official Microsoft .NET Foundation package

Performance Considerations ✅

• No negative impact: Patch version with performance improvements
• Isolated usage: Only used in:
  • TUnit.Performance.Tests/ (internal benchmarks)
  • tools/speed-comparison/Tests.Benchmark/ (framework comparison)
• Key improvement: The 0.15.4 release includes "Allow override method/property for ParamsSource" which could enhance benchmark flexibility

Test Coverage ✅

• Comprehensive benchmarking: TUnit has extensive performance test coverage
  • Test discovery benchmarks (TestDiscoveryBenchmarks.cs)
  • Test execution benchmarks (TestExecutionBenchmarks.cs)
  • Framework comparison benchmarks
• AOT compatibility: Benchmarks test both regular and Native AOT scenarios
• No test changes needed: Patch update shouldn't require test modifications

Impact Analysis 📊

Files Using BenchmarkDotNet:

• /TUnit.Performance.Tests/TUnit.Performance.Tests.csproj:13
• /tools/speed-comparison/Tests.Benchmark/Tests.Benchmark.csproj:11

Usage patterns analyzed:

• Standard BenchmarkDotNet attributes ([Benchmark], [GlobalSetup], [MemoryDiagnoser])
• Custom configuration with performance-focused settings
• Multi-target framework support (.NET 8.0, .NET 9.0, Native AOT)

🎯 Recommendation

APPROVE - This is a safe dependency update that:

• ✅ Maintains compatibility with existing benchmarks
• ✅ Provides potential performance improvements
• ✅ Follows proper semantic versioning (patch update)
• ✅ Has no security implications
• ✅ Doesn't affect production TUnit code

Optional follow-up: Update BenchmarkDotNet.Annotations to 0.15.4 for version consistency.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: BenchmarkDotNet 0.15.3 → 0.15.4 Update ✅

Todo List:

• Examine the changed file (Directory.Packages.props)
• Review BenchmarkDotNet usage in the codebase
• Analyze potential impact on TUnit's benchmarks
• Check for consistency with related packages
• Assess security and compatibility considerations
• Provide comprehensive review feedback

---

✅ Overall Assessment: APPROVE

This is a low-risk patch update that should be safe to merge. The dependency update only affects development/benchmarking tooling and doesn't impact TUnit's runtime or production code.

Code Quality & Best Practices ✅

• Clean change: Single line update in centralized package management (Directory.Packages.props:10)
• Proper versioning: Uses centralized package management correctly
• Consistent pattern: Follows established dependency update patterns
• Version alignment: BenchmarkDotNet.Annotations is already at 0.15.4, maintaining consistency

Potential Issues ⚠️

None identified - This is a straightforward patch version update with no breaking changes expected.

Security Concerns ✅

• No security risks: BenchmarkDotNet is used only in test/benchmark projects
• Limited scope: Only affects performance testing infrastructure
• Trusted source: Official .NET Foundation package with established security practices

Performance Considerations ✅

• No negative impact: Patch version typically includes performance improvements and bug fixes
• Isolated usage: Only used in:
  • TUnit.Performance.Tests/ (internal benchmarks at /TUnit.Performance.Tests/TUnit.Performance.Tests.csproj:13)
  • tools/speed-comparison/Tests.Benchmark/ (framework comparison at /tools/speed-comparison/Tests.Benchmark/Tests.Benchmark.csproj:11)
• Key improvement: The 0.15.4 release includes "Allow override method/property for ParamsSource" which could enhance benchmark flexibility

Test Coverage ✅

• Comprehensive benchmarking: TUnit has extensive performance test coverage
  • Test discovery benchmarks (TestDiscoveryBenchmarks.cs) - Tests reflection vs delegate performance
  • Test execution benchmarks (TestExecutionBenchmarks.cs) - Measures execution overhead
  • Framework comparison benchmarks for competitive analysis
• AOT compatibility: Benchmarks test both regular and Native AOT scenarios (RuntimeMoniker.Net80, RuntimeMoniker.NativeAot80)
• No test changes needed: Patch update shouldn't require test modifications

Impact Analysis 📊

BenchmarkDotNet Usage Patterns:

• Standard BenchmarkDotNet attributes ([Benchmark], [GlobalSetup], [MemoryDiagnoser])
• Custom configuration with performance-focused settings (BenchmarkConfig.cs)
• Multi-target framework support (.NET 8.0, .NET 9.0, Native AOT)
• Extensive use of advanced features like baseline comparisons and custom columns

Critical Performance Benchmarks:

• Discovery benchmarks: Compare reflection vs source-generated approaches
• Execution benchmarks: Measure delegate vs reflection performance
• Hook benchmarks: Test setup/teardown overhead
• Framework comparison: Position TUnit against competitors

Release Notes Review ✅

The 0.15.4 release focuses on:

• ParamsSource improvements: Allow override method/property for ParamsSource (#2832)
• This enhancement could benefit TUnit's parameterized benchmarks if they use ParamsSource in the future

🎯 Recommendation

APPROVE - This is a safe dependency update that:

• ✅ Maintains full compatibility with existing benchmark infrastructure
• ✅ Provides potential performance and flexibility improvements
• ✅ Follows proper semantic versioning (patch update)
• ✅ Has no security implications for production code
• ✅ Doesn't affect TUnit's core functionality or user-facing features

The update aligns with TUnit's commitment to performance excellence by keeping benchmarking tools current.

[claude]

Claude finished @thomhurst's task —— View job

---

PR Review: BenchmarkDotNet 0.15.3 → 0.15.4 Update ✅

Todo List:

• Examine the changed file (Directory.Packages.props)
• Review BenchmarkDotNet usage in the codebase
• Analyze potential impact on TUnit's benchmarks
• Check for security and compatibility considerations
• Assess version consistency with related packages
• Provide comprehensive review feedback

---

✅ Overall Assessment: APPROVE

This is a low-risk patch update that should be safe to merge. The dependency update only affects development/benchmarking tooling and doesn't impact TUnit's runtime or production code.

Code Quality & Best Practices ✅

• Clean change: Single line update in centralized package management (Directory.Packages.props:10)
• Proper versioning: Uses centralized package management correctly
• Version consistency: Both BenchmarkDotNet and BenchmarkDotNet.Annotations are aligned at 0.15.4
• Consistent pattern: Follows established dependency update patterns

Potential Issues ✅

None identified - This is a straightforward patch version update with no breaking changes expected.

Security Concerns ✅

• No security risks: BenchmarkDotNet is used only in test/benchmark projects
• Limited scope: Only affects performance testing infrastructure
• Trusted source: Official .NET Foundation package with established security practices

Performance Considerations ✅

• No negative impact: Patch version typically includes performance improvements and bug fixes
• Isolated usage: Only used in:
  • TUnit.Performance.Tests/ (internal benchmarks at TUnit.Performance.Tests.csproj:13)
  • tools/speed-comparison/Tests.Benchmark/ (framework comparison at Tests.Benchmark.csproj:11)
• Key improvement: The 0.15.4 release includes "Allow override method/property for ParamsSource" which could enhance benchmark flexibility

Test Coverage & Benchmark Infrastructure ✅

TUnit has comprehensive benchmark coverage:

Internal Performance Tests (TUnit.Performance.Tests/):

• Discovery benchmarks (TestDiscoveryBenchmarks.cs:10-11) - Tests reflection vs delegate performance with RuntimeMoniker.Net80 and RuntimeMoniker.NativeAot80
• Execution benchmarks (TestExecutionBenchmarks.cs:10-11) - Measures execution overhead across different approaches
• Data source benchmarks (DataSourceBenchmarks.cs:11-12) - Tests data provider performance patterns
• AOT compatibility: All benchmarks support Native AOT scenarios

Framework Comparison Tests (tools/speed-comparison/Tests.Benchmark/):

• Runtime benchmarks (RuntimeBenchmarks.cs:7-8) - Competitive analysis against other frameworks
• Build benchmarks (BuildBenchmarks.cs) - Compare build-time performance
• Custom configuration (BenchmarkConfig.cs:10-31) - Advanced BenchmarkDotNet setup with custom columns and exporters

Advanced Usage Patterns:

• Standard attributes: [Benchmark], [GlobalSetup], [MemoryDiagnoser], [JsonExporterAttribute.Full]
• Multi-target frameworks: .NET 8.0, .NET 9.0, Native AOT
• Custom job configuration with Job.Default.WithRuntime(CoreRuntime.Core90)
• Baseline comparisons with [Benchmark(Baseline = true)]
• Category-based organization with [BenchmarkCategory]

Impact Analysis 📊

No ParamsSource Usage Found: TUnit's benchmarks don't currently use the ParamsSource feature that was improved in 0.15.4, so the specific enhancement won't impact existing benchmarks but could be beneficial for future use.

README Impact: The README contains benchmark results showing "BenchmarkDotNet v0.15.3" in headers - these will automatically update when benchmarks are re-run with 0.15.4.

Critical Performance Benchmarks Analyzed:

• Discovery performance: Reflection vs source-generated approaches (TestDiscoveryBenchmarks.cs:33-65)
• Execution performance: Delegate vs reflection overhead (TestExecutionBenchmarks.cs:56-144)
• Data source performance: Various data provider patterns (DataSourceBenchmarks.cs:40-114)
• Framework comparison: TUnit positioning against competitors (RuntimeBenchmarks.cs)

Release Notes Review ✅

The 0.15.4 release focuses on:

• ParamsSource improvements: Allow override method/property for ParamsSource (#2832)
• This enhancement maintains full backward compatibility and doesn't affect TUnit's current usage patterns

🎯 Recommendation

APPROVE - This is a safe dependency update that:

• ✅ Maintains full compatibility with TUnit's extensive benchmark infrastructure
• ✅ Provides potential performance and flexibility improvements
• ✅ Follows proper semantic versioning (patch update)
• ✅ Has no security implications for production code
• ✅ Doesn't affect TUnit's core functionality or user-facing features
• ✅ Keeps version consistency between BenchmarkDotNet and BenchmarkDotNet.Annotations

The update aligns with TUnit's commitment to performance excellence by keeping benchmarking tools current and supports the framework's dual execution modes (source-generated vs reflection) benchmarking strategy.