Skip to content

Add a test harness, CI and current package metadata - #1

Merged
2rdzy merged 1 commit into
masterfrom
chore/test-harness
Oct 6, 2026
Merged

2rdzy merged 1 commit into
masterfrom
chore/test-harness

Conversation

@2rdzy

@2rdzy 2rdzy commented Oct 5, 2026

Copy link
Copy Markdown
Owner

There were no tests (npm test printed an error). This adds the harness the following fixes need.

  • node:test tests against a small in-process Electrum server over TCP and TLS: version negotiation, results, server errors, concurrent requests, batches, notifications, and close. The TLS fixture (test/fixtures) is a test-only self-signed certificate for localhost / 127.0.0.1; its key protects nothing.
  • GitHub Actions runs the tests on Node 18, 20 and 22.
  • package.json: repository, bugs and homepage point at this fork; engines requires Node 18 or later (it said 6); only index.js and lib are published; npm test runs the tests.

No behaviour change. Checked locally: 14 tests pass on Node 22.

Add node:test tests against a small in-process Electrum server over TCP and
TLS (with a committed, test-only certificate), covering requests, errors,
concurrency, batches, notifications and close. Run them in CI on Node 18, 20
and 22.

Point the repository, bugs and homepage fields at this fork, require Node 18
or later, and publish only index.js and lib.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant