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

check_application.sh: run only the API test files you name

Aperta
  • Qualcosa non va?
#424 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
75/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker-compose, shell, typescript
Ambito
developer-experience, testing

Direzione di ricerca

Start with scripts/check_application.sh, lines 55-70, where the build, stack start and $compose run --rm test step run every API test file. The test service's default command is in docker/compose.source.yaml around line 320. Copy the named-module handling from scripts/check_ui.sh (lines 6-7 and 64-68). Done means: passing test paths runs only those files and skips the e2e and restart checks, a missing path exits 2 before Docker starts, and no-argument behaviour is unchanged.

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

Descrizione

good first issue

To check one change to an API test that needs the database or the API, a contributor must run the whole Docker suite: every API test file, then every browser and restart check. Only the *-core.test.ts files can run on their own, in the test image. ./scripts/check_ui.sh already accepts the modules to run (#204); ./scripts/check_application.sh should accept API test files the same way.

Where to look

  • scripts/check_application.sh (lines 55–70): build, stack start, VAPID keys, then $compose run --rm test runs every API test file; the e2e and restart checks follow.
  • docker/compose.source.yaml (line 320): the test service's default command, tsx --test --test-concurrency=1 tests/app/*.test.ts.
  • scripts/check_ui.sh (lines 6–7 and 64–68): how named modules are handled there.
  • docs/development/architecture.md (§ Tests) and docs/CONTRIBUTING.md (§ Verify your change).

Acceptance criteria

  • ./scripts/check_application.sh tests/app/search.test.ts (one or more paths under app/tests/app/, as seen from app/) runs only those files in the test service, with the same stack and environment, and skips the e2e and restart checks; it says so in its output.
  • A path that does not exist is refused before Docker starts, with exit status 2.
  • Without arguments the script behaves exactly as today.
  • CONTRIBUTING § Verify your change shows the one-file command, replacing its interim note that only a *-core.test.ts file can run on its own (added for #306).

How to check
Run ./scripts/check_application.sh tests/app/search.test.ts, a missing path, and the script without arguments (set FLUX_TEST_PORT/FLUX_TEST_MAILPIT_PORT if the defaults are taken). Then python3 scripts/check_agent_setup.py, python3 -m unittest discover -s tests -p 'test_*.py', git diff --check.

New to Flux? Start with CONTRIBUTING. Comment here to say you are taking it.

Lingua principale
TypeScript
Stelle
3
Fork
0
Merge medio
18h 3m
PR unite (30g)
254

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 ColdPhase/flux

Tutte le issue di ColdPhase/flux

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.