-
Notifications
You must be signed in to change notification settings - Fork 971
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
Add unit tests to System.Windows.Forms.Design.* components #720
Comments
This issue is now marked as "up for grabs", and we’re looking for a community volunteer to work on this issue. If we receive no interest in 120 days, we will close the issue. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Hey @JuditRose, can I look into this? Is this still active? |
@LeafShi1 - Could you please review our current code coverage for System.Windows.Forms.Design namespace and add all public classes and Editords that are not covered by unit tests to the list in this bug description. |
Tracking this issue with issue #10773 |
Add unit tests (if not exists) for
System.Windows.Forms.Design.WindowsFormsDesignerOptionService
System.Windows.Forms.Design.MenuCommands
System.Windows.Forms.Design.ComponentTray
System.Windows.Forms.Design.DesignerOptions
Epic: #716
Related issues: #221, #585
Related PRs: #632
The text was updated successfully, but these errors were encountered: