[Feature] Add smoke coverage for release VSIX artifact handling
维护者通常 1 天内回复
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- typescript
调研方向
Start with the gulp release task, which removes old VSIX files and moves the latest package into test/smoke/resources/extension, then read the existing npm run smoke-tests setup. Add a read-only check that the repository root has no VSIX files, the smoke resource directory exists, and it holds exactly one non-empty VSIX. Pull request #3003 is already open against this issue, so check with the maintainers before starting.
由索引模型根据 Issue 内容生成。
描述
Summary
Add a smoke test that validates the final VSIX artifact state after gulp release.
Previously, every version change generated a new VSIX in the repository root without removing older versions. The release task now removes outdated VSIX files and moves the latest package to:
test/smoke/resources/extension
Why this is useful
Without automated coverage, VSIX files from multiple extension versions may accumulate in the repository root.
The smoke test will help detect regressions where:
- Multiple VSIX files remain in the repository root.
- The latest VSIX is not moved to the smoke resource directory.
- An outdated VSIX remains in the smoke resource directory.
Suggested scope
- Verify that the repository root contains no VSIX files after release.
- Verify that the smoke resource directory exists.
- Verify that the smoke resource directory contains exactly one VSIX.
- Verify that the generated VSIX has a non-zero file size.
- Keep the test read-only.
Evidence
Before the release task was updated, each version generated an additional VSIX in the repository root, leaving packages from multiple versions.
The latest VSIX also had to be copied manually to:
test/smoke/resources/extension
The CI pipeline runs gulp release before the smoke tests, making the final artifact state available for validation.
Validation
Run:
gulp release
npm run smoke-tests
Confirm that:
- No VSIX remains in the repository root.
- Exactly one non-empty VSIX exists in
test/smoke/resources/extension. - The VSIX smoke test passes.
- 主要语言
- TypeScript
- 星标
- 2.7k
- 派生
- 298
- 平均合并
- 14 小时 54 分钟
- 30 天内合并 PR
- 28
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/vscode-react-native 的其他 Issue
-
[Feature] Avoid duplicate error notifications可能已有人在做 @erenbati 于 5 天前认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 75/100
microsoft/vscode-react-native#2963 ·
维护者通常 1 天内回复
-
[Feature] Stop Expo Go installation when Quick Pick is canceled可能已有人在做 @erenbati 于 20 天前认领。 未关闭enhancement
难度 2/5 1-3 小时 新手友好度 88/100
microsoft/vscode-react-native#2959 ·
维护者通常 1 天内回复
-
enhancement follow-up
难度 2/5 1-3 小时 新手友好度 88/100
microsoft/vscode-react-native#2951 ·
维护者通常 1 天内回复
-
[Feature] Expo Doctor output is lost when diagnostics fail可能已有人在做 @erenbati 于 20 天前认领。 未关闭enhancement
难度 3/5 1-2 天 新手友好度 72/100
microsoft/vscode-react-native#2957 ·
维护者通常 1 天内回复
-
[Feature] Incorrect log message when Metro process termination fails可能已有人在做 @erenbati 于 5 天前认领。 未关闭enhancement follow-up
难度 3/5 1-2 天 新手友好度 68/100
microsoft/vscode-react-native#2952 ·
维护者通常 1 天内回复
查看 microsoft/vscode-react-native 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 75/100
siyuan-note/siyuan#20629 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Volume eject does not refuse system, root or /home mounts可能已有人在做 @bernardopg 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
spacedriveapp/spacedrive#3159 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
melgarafael/DeskcommCRM#3000 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
callstackincubator/simlock#639 ·
维护者通常 1 天内回复