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

Share the test-Chrome resolver with the client browser tests and ci-warm-test-chrome.sh

Closed
#12,315 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@atomantic is already working on this.

Since Oct 19, 2026.

  • #12319 by @atomantic — merged

Assessment

This issue has not been assessed yet.

Description

code-quality effort:medium in-progress model:light planner:sonnet-5-5 tests

Follow-up to #12293. Roughly 12 client/src/** browser tests still carry their own Chrome candidate list (rg executablePath client/src), and scripts/ci-warm-test-chrome.sh has a shell copy. Next step: have the client tests import resolveTestChrome from server/lib/browserSuiteGate.js (or a client-side shared helper) and derive the shell list from one source. Acceptance: rg 'chromium.executablePath\(\)' client server scripts matches only the shared resolver; browser suites stay green.

Related to #12293

Dominant language
JavaScript
Stars
38
Forks
32
Avg merge
31m
Merged PRs (30d)
995

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 atomantic/PortOS

All issues in atomantic/PortOS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.