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

Tests: integration coverage for startHarper/teardownHarper against a real Harper

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
testing

Research direction

Start in the test/ suite and the existing fixture-based unit-test harness, then review startHarper, teardownHarper, killHarper, and setupHarperWithFixture. Configure the harper-integration-test-setup-loopback pool and a real Harper peer dependency, or skip when no Harper build is available. Done means the happy path, teardown cleanup, restart without EADDRINUSE, and pre-installed fixture coverage run successfully.

Written by the indexing model from the issue text.

Description

enhancement

Summary

Follow-up from #8 / #9. The new test/ suite covers runHarperCommand, killHarper, and the port helpers in isolation, but the lifecycle orchestration (startHarper / teardownHarper) is not exercised end-to-end because that needs a real Harper instance (the package's harper peer dependency) and loopback-pool setup. Worth adding as a separate integration-test layer.

Coverage to add

  • Happy path — startHarper(ctx) → make a request against ctx.harper.httpURL/operationsAPIURL → teardownHarper(ctx); assert the instance came up and was cleaned up.
  • Teardown orchestration — teardownHarper kills the process, waits for the fixed ports to free, releases the loopback address back to the pool, and removes the data root dir.
  • Race 2 restart path — killHarper(ctx) followed by startHarper(ctx) reusing the same hostname succeeds without EADDRINUSE (verifies the port-wait-before-spawn added in #9).
  • setupHarperWithFixture — a pre-installed component is available on first boot.

Notes

Needs a real Harper available (peer dependency) and the loopback pool configured (harper-integration-test-setup-loopback), so this likely lives in a separate harness from the fixture-based unit tests in test/. May be best run only where a Harper build is present (and skipped otherwise).


🤖 Generated with Claude Code

Dominant language
TypeScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

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 HarperFast/integration-testing

All issues in HarperFast/integration-testing

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.