[SqlClient] Fix test for .NET Framework

[martincostello]

Changes

Update test cases for different behaviour between .NET Framework and .NET.

Discovered after I ran dotnet test on my Windows 11 machine.

Merge requirement checklist

• CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)
• Unit tests added/updated
• Appropriate CHANGELOG.md files updated for non-trivial changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.82%. Comparing base (71655ce) to head (0d456ae).
Report is 880 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2826       +/-   ##
===========================================
+ Coverage   73.91%   87.82%   +13.91%     
===========================================
  Files         267        9      -258     
  Lines        9615      460     -9155     
===========================================
- Hits         7107      404     -6703     
+ Misses       2508       56     -2452     

Flag	Coverage Δ
unittests-Instrumentation.SqlClient	87.82% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 270 files with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull Request Overview

Updates the SqlClient integration tests to handle differing stored-procedure behavior between .NET Framework and .NET by adjusting the InlineData parameters under conditional compilation.

• Added #if NETFRAMEWORK/#else around stored-procedure InlineData to use a null expected operation name on .NET Framework
• Split and adjusted test data for each framework case

Comments suppressed due to low confidence (2)

test/OpenTelemetry.Instrumentation.SqlClient.Tests/SqlClientIntegrationTests.cs:32

• Add a brief comment above this conditional block explaining why .NET Framework uses a null expected operation name, so future maintainers understand the behavioral difference.

#if NETFRAMEWORK

test/OpenTelemetry.Instrumentation.SqlClient.Tests/SqlClientIntegrationTests.cs:33

• [nitpick] Add tests for toggling other flags (e.g., statement collection or parameter inclusion) in the stored-procedure scenario, similar to the text-command cases, to ensure consistent test coverage.

[InlineData(CommandType.StoredProcedure, "sp_who", false, null)]

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[TimothyMothra]

Does this test fail on NetFx ?

I'm trying to determine if we have problem with the CI.

[martincostello]

Before the fix, it failed 100% of the time on my laptop, which is how I found it.

I did have a similar thought as to why CI wasn't failing, but I couldn't see anything obvious that explained it.