PowerShell / PowerShell/PSScriptAnalyzer
Investigate/Fix test failure on PowerShell Core
未關閉
還沒有人認領這個 Issue。
Area - Build
Area - Rules
- 主要語言
- C#
- 星號
- 2.2k
- 分支
- 415
- 平均合併
- 13 小時 1 分鐘
- 30 天內合併 PR
- 2
描述
- The
"suggests corrections for AliasesToExport with wildcardofUseManifestExportFieldsis currently set as pending when tests are being run using the coreclr.
This tests needs to be looked into and possibly fixed.
The test is here:
https://github.com/PowerShell/PSScriptAnalyzer/blob/021711eae27a2bd00165f30c6c568a78f448870a/Tests/Rules/UseToExportFieldsInManifest.tests.ps1#L86 - There are 9 test failures using PowerShell Core on Windows and Ubuntu but they do not fail in AppVeyor for some reason. Those tests were always failing, even when going back to an old commit like
9e37dd34e8564dc7470dda1e0d2596de37bcd679in January. Therefore those failures are to be considered technical debt. Until we know why AppVeyor lets them pass and fix them afterwards, we have to more diligent with running tests locally or on VSTS using PowerShell Core to make sure that we do not introduce regression. The test failures are:


貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從所引用測試中的 Tests/Rules/UseToExportFieldsInManifest.tests.ps1 開始,並在 Windows 和 Ubuntu 上使用 PowerShell Core 執行測試套件。將回報的失敗與 AppVeyor 結果進行比較,並判斷列出的九個失敗是測試問題還是環境問題。當這些失敗獲得解釋,且受影響的測試已適當修正或更新時,即視為完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- powershell
- 領域
- testing-qa
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100