dotnet/roslyn

Sample unit test code doesnt verify diagnostics at line/column start

Open

#1,641 建立於 2015年3月27日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)C# (20,414 star) (4,257 fork)batch import
Area-CompilersBugTesthelp wanted

描述

The issue is in here and here. If the line/column is 0 unit tests will not care if the expected line/column matches that. Also see https://github.com/DotNetAnalyzers/StyleCopAnalyzers/pull/569.

貢獻者指南

技術棧
csharp
領域
testingtooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
C# basicsunit testing concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
The issue points to two specific lines in DiagnosticVerifier.cs (lines 193 and 204) where the verification of diagnostics fails when line/column is 0. A similar fix was implemented in StyleCopAnalyzers PR #569, which can serve as a reference. The fix should ensure that when line/column is 0, the expected values are still compared. No linked PR or assignees exist, so work can start independently.