Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature] Add smoke coverage for release VSIX artifact handling

Aperta
  • Qualcosa non va?
#3,004 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@EmmaYuan1015 ci sta già lavorando.

Dal 15/10/2026.

  • #3003 di @EmmaYuan1015 — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
typescript
Ambito
release, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
2.7k
Fork
298
Merge medio
18h 34m
PR unite (30g)
30

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/vscode-react-native

Tutte le issue di microsoft/vscode-react-native

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.