-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Adds coverage for ComponentTray
#13396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds coverage for ComponentTray
#13396
Conversation
Related dotnet#10773 - Adds coverage for `ComponentTray`. - None - No - Minimal - Unit tests - 10.0.100-preview.3.25201.16
|
Drafted because will add more tests. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #13396 +/- ##
===================================================
+ Coverage 62.72868% 62.96868% +0.24000%
===================================================
Files 1561 1563 +2
Lines 159997 160132 +135
Branches 14918 14919 +1
===================================================
+ Hits 100364 100833 +469
+ Misses 58857 58524 -333
+ Partials 776 775 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
ComponentTrayComponentTray
...ystem.Windows.Forms.Design/tests/UnitTests/System/Windows/Forms/Design/ComponentTrayTests.cs
Show resolved
Hide resolved
|
In my opinion, the component try is nothing we should officially support in the runtime. I would not like to take this. Closing this. Feel free to reopen, if you disagree. @merriemcgaw FYI. @ricardobossan, sorry for the effort you already did. @Olina-Zhang, @LeafShi1, @merriemcgaw FYI. |
Related #10773
Proposed changes
ComponentTray.Customer Impact
Regression?
Risk
Test methodology
Test environment(s)
Microsoft Reviewers: Open in CodeFlow