Test Runners

Hone uses per-package test runners. There is no monorepo-level test command — each package must be tested independently.

Test Matrix

Running Tests

All tests in a package

cd hone-core && bun test
cd hone-editor && bun test
cd hone-terminal && bun test
cd hone-relay && bun test
cd hone-build && bun test
cd hone-themes && npm test
cd hone-extensions && npm test
cd hone-api && npm test

A single test file

cd hone-editor && bun test tests/buffer.test.ts

With Bun, pass the file path as an argument. Bun matches on filename, so partial names also work:

bun test buffer       # runs all test files containing "buffer" in the name

Type checking

cd <package> && bun run typecheck
# or
npx tsc --noEmit

Important: Use the Correct Runner

The runner matters. Do not use npx vitest or npx jest in Bun-based packages — they will fail because test files import from bun:test, which only Bun provides.

Writing Tests (Bun Packages)

import { describe, it, expect, beforeEach } from 'bun:test';

describe('PieceTable', () => {
  let table: PieceTable;

  beforeEach(() => {
    table = new PieceTable('hello world');
  });

  it('should insert text', () => {
    table.insert(5, ' beautiful');
    expect(table.getText()).toBe('hello beautiful world');
  });

  it('should delete text', () => {
    table.delete(5, 6);
    expect(table.getText()).toBe('hello');
  });
});

What Each Package Tests