Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#424 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
75/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
docker-compose, shell, typescript
Domain
developer-experience, testing

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
22h 53m
Merged PRs (30d)
272

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.