Files
vue-tui/packages/testing
Yunfei He 90dc89272e fix(ci): include runtime and testing unit tests in vp run ci
The ci graph's test:integration task runs `vp run -r test:integration`, but
that script only existed in runtime-tests, so `vp run -r` silently skipped
packages/runtime (11 files, 309 tests) and packages/testing (2 files, 7 tests)
— their unit tests never ran in CI.

Give both packages a test:integration script (= vp test) and make their `test`
compose it, mirroring runtime-tests. `vp run -r test:integration` now covers
all three packages. PTY stays its own branch (no double-run).

Verified: `CI=true vp run ci` on a fresh checkout runs runtime (309) + testing
(7) + runtime-tests (756), exit 0.

Reported-by: @reviewer on PR #25
2026-05-29 16:54:13 +08:00
..

@vue-tui/testing

Early stage — under active development. Bug reports welcome, but not recommended for production use yet.

Test harness for vue-tui — render Vue 3 terminal components, simulate input, assert frames. Like @testing-library, but for the terminal.

npm version npm downloads

Why

  • Isolated terminal — renders into a fake TTY, no real terminal needed
  • Input simulation — inject keystrokes that reach useInput handlers
  • Frame snapshots — assert exact visual output with lastFrame() and frames[]
  • Auto-cleanup — unmounts all rendered apps after each test (requires Vitest globals: true)

Install

Assumes @vue-tui/runtime and vue are already installed in your project.

npm install -D @vue-tui/testing

Quick Start

import { defineComponent, shallowRef } from "vue";
import { expect, test } from "vitest";
import { render } from "@vue-tui/testing";
import { Box, Text, useInput } from "@vue-tui/runtime";

test("counter responds to + and - keys", async () => {
  const Counter = defineComponent(() => {
    const count = shallowRef(0);
    useInput((input) => {
      if (input === "+") count.value++;
      if (input === "-") count.value--;
    });
    return () => (
      <Box>
        <Text>Count: {count.value}</Text>
      </Box>
    );
  });

  const { lastFrame, stdin } = await render(Counter);
  expect(lastFrame()).toContain("Count: 0");

  await stdin.write("+");
  expect(lastFrame()).toContain("Count: 1");

  await stdin.write("-");
  expect(lastFrame()).toContain("Count: 0");
});

API

render(component, options?)

Mounts a component in a fake terminal environment. Returns a RenderResult.

Option Type Default Description
columns number 100 Terminal width in columns
rows number 100 Terminal height in rows
props object — Props passed to the root component
exitOnCtrlC boolean false Enable Ctrl+C exit handling

RenderResult

Property / Method Description
lastFrame(opts?) Latest rendered frame as a string
frames Array of all captured frame snapshots
stdin.write(data) Inject input (reaches useInput handlers)
terminal Fake terminal — columns, rows, resize(), rawMode
unmount() Tear down the app
waitUntilExit() Settles when the app exits (rejects if exit(error))
waitUntilRenderFlush() Resolves after the next render cycle completes

cleanup()

Unmounts all rendered apps. Auto-registered as a Vitest afterEach hook when globals: true is set. Call manually if your test runner doesn't expose a global afterEach.

License

MIT