Missing unit tests coverage of public methods in Design namespace #10773
Comments
|
There's also this previous list of controls, that were added on #10453 :
|
|
@SimonZhao888 - could you please use this bug only for public classes from System.Windows.Forms.Design namespace - https://github.com/dotnet/winforms/tree/main/src/System.Windows.Forms.Design/src? And then add help-wanted label. We will use this bug to track tests added by contributors. |
Tanya-Solyanik
changed the title
|
Also remember the goal here isn't to increase code coverage. The goal is to identify user/developer scenarios which people are depending on today, and add tests that make it unlikely we would break those users in the future. Every added test should be written from the perspective of what someone using WinForms will try to do, and validate they will get the expected result. The difference is subtle for public APIs, but for internal APIs that aren't always obvious to invoke, it becomes important to try and write tests targeting those features against public APIs where possible. Tests that exercise behavior using public APIs better reflect user behavior and the tests are much easier to understand if a failure ever shows up. |
ghost
modified the milestones:
|
This issue is now marked as "help wanted", and we’re looking for a community volunteer to work on this issue. If we receive no interest in 180 days, we will close the issue. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
dotnet-policy-service
bot
added
the
🚧 work in progress
Related #10773 Add unit test DesignerVerbToolStripMenuItemTests.cs for public properties and method of the DesignerVerbToolStripMenuItem.
Related #10773 Proposed changes Add unit test MaskedTextBoxDesignerActionListTests.cs for public properties and method of the MaskedTextBoxDesignerActionList. Enable nullability in MaskedTextBoxDesignerActionListTests.cs.
* Add unit tests for ControlDesigner.TransparentBehavior Related #10773
Related #10773 Proposed changes Add unit test DataGridViewAddColumnDialogTests.cs for public properties and method of the DataGridViewAddColumnDialog. Enable nullability in DataGridViewAddColumnDialogTests.cs.
Related #10773 Proposed changes Add unit test LinkAreaEditorTests.cs for public properties and method of the LinkAreaEditor. Enable nullability in LinkAreaEditorTests.cs.
* Add unit tests for ControlDesigner.TransparentBehavior Related dotnet#10773
Related dotnet#10773 Proposed changes Add unit test DataGridViewAddColumnDialogTests.cs for public properties and method of the DataGridViewAddColumnDialog. Enable nullability in DataGridViewAddColumnDialogTests.cs.
…otnet#12664) Related dotnet#10773 Proposed changes Add unit test ControlDesigner.ControlDesignerAccessibleObjectTests.cs for public properties and method of the ControlDesigner.ControlDesignerAccessibleObject. Enable nullability in ControlDesigner.ControlDesignerAccessibleObjectTests.cs.
Related dotnet#10773 Proposed changes Add unit test LinkAreaEditorTests.cs for public properties and method of the LinkAreaEditor. Enable nullability in LinkAreaEditorTests.cs.
We are in the process of adding unit tests for all public methods to improve the test coverage of code. Here is a list categorized by namespace.
System.Windows.Forms.Design
FormatControl.CurrencyFormatType.cs(private class)FormatControl.CustomFormatType.cs(private class)FormatControl.DateTimeFormatType.cs(private class)FormatControl.NoFormattingFormatType.cs(private class)FormatControl.NumericFormatType.cs(private class)FormatControl.ScientificFormatType.cs(private class)The text was updated successfully, but these errors were encountered: