[dotnet] [test] Add NUnit analyzer#17522
Conversation
Review Summary by QodoAdd NUnit analyzer and fix test code issues
WalkthroughsDescription• Add NUnit.Analyzers dependency to test projects • Fix resource disposal using Dispose instead of Quit • Make test fixture classes abstract to prevent instantiation • Fix test assertions to use correct property access patterns • Refactor test code to extract variables for clarity Diagramflowchart LR
A["NUnit.Analyzers<br/>Dependency"] --> B["Test Projects<br/>Updated"]
C["Resource Disposal<br/>Quit → Dispose"] --> D["Test Cleanup<br/>Improved"]
E["Abstract Fixtures<br/>BiDiTestFixture<br/>DevToolsTestFixture"] --> F["Inheritance<br/>Enforced"]
G["Assertion Fixes<br/>Property Access<br/>Variable Extraction"] --> H["Test Code<br/>Corrected"]
File Changes1. dotnet/paket.dependencies
|
|
Thank you, @nvborisenko for this code suggestion. The support packages contain example code that many users find helpful, but they do not necessarily represent After reviewing the change, unless it is a critical fix or a feature that is needed for Selenium We actively encourage people to add the wrapper and helper code that makes sense for them to their own frameworks. |
|
Persistent review updated to latest commit 28ea17f |
Code Review by Qodo
1.
|
|
Persistent review updated to latest commit 6c46f10 |
|
Persistent review updated to latest commit 4fead34 |
🤖 AI assistance
🔄 Types of changes