Testing and verified results

August 15, 2026 · View on GitHub

English | 简体中文

Unit checks

npm run check

The unit suite validates command invocation, seven-tool registration, allowedRoots, nested asset/output protection, output-symlink rejection, and conversion of Timeline Studio ok:false responses into Harness tool errors.

End-to-end test

TIMELINE_STUDIO_ROOT=/absolute/path/to/web_player npm run test:e2e

The test uses the real Cordis Context, @deepseek-ai/dsh-system-prompt, and @deepseek-ai/dsh-tools rc.6 execution pipeline. It performs this workflow without an LLM or API key:

  1. Mount the production plugin and verify all seven model-visible schemas.
  2. Create a portable .timeline archive in a temporary directory.
  3. Inspect revision 0 and the original 16:9 ratio.
  4. Generate a real PNG with FFmpeg.
  5. Diff an edit plan that imports the PNG and changes the ratio to 9:16; verify that diff writes nothing.
  6. Apply the plan and reopen the output project at revision 1.
  7. Inspect the Visuals track, visual clip, and transcript through Harness tools.
  8. Render a real 180×320 MP4 through Timeline Studio.
  9. Decode/probe the output with ffprobe and verify duration and dimensions.
  10. Attempt an out-of-root read and verify Harness returns isError: true.

Last verified environment

  • Date: 2026-08-15
  • Node.js: 24.11.1
  • DeepSeek Harness tool packages: 0.1.0-rc.6
  • Cordis: 4.0.1
  • FFmpeg/ffprobe: 8.0.1
  • Unit tests: 7 passed
  • End-to-end tests: 1 passed

All generated media and projects are written to the operating system temporary directory; no test media is retained in the repository.