Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Feature] Add smoke coverage for release VSIX artifact handling

Abierto
  • ¿Algo no está bien?
#3,004 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@EmmaYuan1015 ya está trabajando en esto.

Desde el 15/10/2026.

  • #3003 de @EmmaYuan1015 — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
release, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

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.
Lenguaje dominante
TypeScript
Estrellas
2.7k
Forks
298
Merge medio
18 h 34 min
PR fusionados (30 d)
30

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/vscode-react-native

Todos los issues de microsoft/vscode-react-native

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.