Add code coverage for ListViewDesigner

[Zheng-Li01]

Related #10773

Proposed changes

Add unit test file: ListViewDesignerrTests.cs for public methods & properties of the ListViewDesigner.cs

Microsoft Reviewers: Open in CodeFlow

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.55644%. Comparing base (1d61434) to head (653f524).
Report is 22 commits behind head on main.

Additional details and impacted files

@@                 Coverage Diff                 @@
##                main      #13301         +/-   ##
===================================================
+ Coverage   62.19645%   62.55644%   +0.35999%     
===================================================
  Files           1556        1560          +4     
  Lines         159366      159675        +309     
  Branches       14854       14904         +50     
===================================================
+ Hits           99120       99887        +767     
+ Misses         59495       59019        -476     
- Partials         751         769         +18     

Flag	Coverage Δ
Debug	62.55644% <100.00000%> (+0.35999%)	⬆️
integration	11.31915% <ø> (+0.01856%)	⬆️
production	40.72577% <ø> (+0.38926%)	⬆️
test	95.69057% <100.00000%> (+0.02333%)	⬆️
unit	38.12645% <ø> (+0.43402%)	⬆️

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

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

Comments suppressed due to low confidence (2)

src/System.Windows.Forms.Design/tests/UnitTests/System/Windows/Forms/Design/ListViewDesignerTests.cs:107

• [nitpick] The test 'ListViewDesigner_Initialize_HooksChildHandles_WhenViewIsDetails' only asserts that the designer instance is not null, which does not verify that child handles are actually hooked. It is recommended to add assertions that check for specific properties or events that confirm the child handles have been hooked when the view is set to Details.

public void ListViewDesigner_Initialize_HooksChildHandles_WhenViewIsDetails()

src/System.Windows.Forms.Design/tests/UnitTests/System/Windows/Forms/Design/ListViewDesignerTests.cs:117

• [nitpick] The test 'ListViewDesigner_Initialize_DoesNotHookChildHandles_WhenViewIsNotDetails' only asserts that the designer instance is not null. It would be more effective to verify that no child handle-related actions occur when the view is not set to Details.

public void ListViewDesigner_Initialize_DoesNotHookChildHandles_WhenViewIsNotDetails()

[ricardobossan]

Other than small comments, LGTM!

[ricardobossan]

Thank you!

[Tanya-Solyanik]

Thank you! Nice catch that this file was in a wrong folder.