-
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
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. |
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. |
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! |
Related #10773 Add unit test PanelDesignerTests.cs for public properties and method of the PanelDesigner.cs Enable nullability in PanelDesignerTests.cs
Related #10773 Proposed changes Add unit test file: TabPageDesignerTests.cs for public properties of the TabPageDesigner.cs. Enable nullability in TabPageDesignerTests.cs.
Related dotnet#10773 ## Proposed changes - Adds code coverage for `RichTextBoxActionList` - Coverage for the `EditLines()` method could not be added. The dependent method `EditorServiceContext.EditValue(_designer, Component!, "Lines")` is static and could not be mocked, and the dialog that opens during its execution requires manual intervention to close. ## Customer Impact - None or succinct description ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-preview.7.24407.12
Add code coverage to RichTextBoxActionList Related to #10773 ## Proposed changes - Adds code coverage for `RichTextBoxActionList` - Coverage for the `EditLines()` method could not be added. The dependent method `EditorServiceContext.EditValue(_designer, Component!, "Lines")` is static and could not be mocked, and the dialog that opens during its execution requires manual intervention to close. Co-authored-by: Ricardo Bossan (BEYONDSOFT CONSULTING INC) (from Dev Box) <v-rbossan@microsoft.com>
Related dotnet#10773 ## Proposed changes - Adds code coverage to `FormatControl`. ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Related #10773 ## Proposed changes - Adds code coverage to `FormatControl`. ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12 Co-authored-by: Ricardo Bossan (BEYONDSOFT CONSULTING INC) (from Dev Box) <v-rbossan@microsoft.com>
Related #10773 Proposed changes Add unit test file: TabControlDesignerTests.cs for public properties and methods of the TabControlDesigner.cs. Enable nullability in TabControlDesignerTests.cs.
Related dotnet#10773 ## Proposed changes - Adds code coverage for `FormatStringDialog`. ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Related #10773 Proposed changes Add unit test ControlDesigner.DesignerControlCollectionTests.cs for public properties and method of the ControlDesigner.DesignerControlCollection. Enable nullability in ControlDesigner.DesignerControlCollection.
Related dotnet#10773 ## Proposed changes - Adds code coverage for `FormatStringDialog`. ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Related #10773 Add unit test TextBoxActionListTests.cs for public properties and method of the TextBoxActionList. Enable nullability in TextBoxActionList.
Related dotnet#10773 ## Proposed changes - Adds code coverage for `FormatStringDialog`. ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Related dotnet#10773 ## Proposed changes - Adds code coverage for `FormatStringDialog`. ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Related dotnet#10773 ## Proposed changes - Adds code coverage to `FormatStringEditor` ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
…ll methods use them Related dotnet#10773 ## Proposed changes - Adds code coverage to `FormatStringEditor` ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Adds code coverage for FormatStringDialog Related #10773 ## Proposed changes - Adds code coverage for `FormatStringDialog`. ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12 Co-authored-by: Ricardo Bossan (BEYONDSOFT CONSULTING INC) (from Dev Box) <v-rbossan@microsoft.com>
Related dotnet#10773 ## Proposed changes - Adds code coverage to `FormatStringEditor` ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Related dotnet#10773 ## Proposed changes - Adds code coverage to `FormatStringEditor` ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Related dotnet#10773 ## Proposed changes - Adds code coverage to `FormatStringEditor` ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12
Adds coverage to FormatStringEditor Related #10773 ## Proposed changes - Adds code coverage to `FormatStringEditor` ## Customer Impact - None ## Regression? - No ## Risk - Minimal ## Test methodology - Unit tests ## Test environment(s) - 9.0.100-rc.1.24452.12 Co-authored-by: Ricardo Bossan (BEYONDSOFT CONSULTING INC) (from Dev Box) <v-rbossan@microsoft.com>
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: