Add code coverage for DataGridViewLinkColumn

[Zheng-Li01]

related #10453

Proposed changes

Add unit tests for DataGridViewLinkColumn.cs to test its properties & methods & events

Microsoft Reviewers: Open in CodeFlow

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.78523%. Comparing base (a3973fb) to head (8829fb8).
Report is 35 commits behind head on main.

Additional details and impacted files

@@                 Coverage Diff                 @@
##                main      #12522         +/-   ##
===================================================
+ Coverage   75.71735%   75.78523%   +0.06788%     
===================================================
  Files           3152        3158          +6     
  Lines         635709      636314        +605     
  Branches       46970       47004         +34     
===================================================
+ Hits          481342      482232        +890     
+ Misses        150932      150619        -313     
- Partials        3435        3463         +28     

Flag	Coverage Δ
Debug	75.78523% <100.00000%> (+0.06788%)	⬆️
integration	18.18211% <ø> (-0.08806%)	⬇️
production	49.38847% <ø> (+0.11096%)	⬆️
test	97.04712% <100.00000%> (-0.00319%)	⬇️
unit	46.60136% <ø> (+0.34665%)	⬆️

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

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[ricardobossan]

Please declare variables as specific types.

Also, please dispose of the created control:

using DataGridViewLinkColumn clone = (DataGridViewLinkColumn)_column.Clone(); 

Both situations happen in other lines of code.

[ricardobossan]

While encapsulating repetitive code is generally a good practice, in unit tests, it can make debugging more challenging and obscure the clear intent of the test. When an error occurs, having test logic directly in the test method makes it easier to trace issues through the call stack without needing to inspect helper methods. While encapsulation may be useful for complex setups or repetitive patterns, prioritizing readability and straightforward error tracking often leads to more maintainable tests.

I’d recommend refactoring the code to inline the logic currently encapsulated in TestPropertySetWithDataGridView directly into the relevant test methods. This will make the tests easier to read and debug, especially when tracking errors.