PowerShell / PowerShell/PSScriptAnalyzer
Investigate/Fix test failure on PowerShell Core
未关闭
还没有人认领这个 Issue。
Area - Build
Area - Rules
- 主要语言
- C#
- 星标
- 2.2k
- 派生
- 414
- 平均合并
- 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