Add end-to-end testing to the definition of done for .NET Analyzers (#…

…5640) * Add end-to-end testing to the definition of done * Update indentation Co-authored-by: Buyaa Namnan <[email protected]> Co-authored-by: Buyaa Namnan <[email protected]>
dotnet · Oct 15, 2021 · 01fd4bf · 01fd4bf
1 parent c87d92f
commit 01fd4bf
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/docs/NetCore_GettingStarted.md b/docs/NetCore_GettingStarted.md
@@ -44,6 +44,9 @@
 - Document for review: severity, default, categorization, numbering, titles, messages, and descriptions.
 - Create the appropriate documentation for [docs.microsoft.com](https://github.com/dotnet/docs/tree/main/docs/fundamentals/code-analysis/quality-rules) within **ONE WEEK**, instructions available on [Contribute docs for .NET code analysis rules to the .NET docs repository](https://docs.microsoft.com/contribute/dotnet/dotnet-contribute-code-analysis).
 - PR merged into `dotnet/roslyn-analyzers`.
+- Validate the analyzer's behavior with end-to-end testing using the command-line and Visual Studio:
+  - Use `dotnet new console` and `dotnet build` from the command-line, updating the code to introduce diagnostics and ensuring warnings/errors are reported at the command-line
+  - Use Visual Studio to create a new project, introduce diagnostics, and observe the warnings/errors/info messages without invoking a build
 
 ## Testing against the Runtime and Roslyn-analyzers repo