跳到正文
cccskills
免费在 GitHub 公开

viewer-smoke

Run the end-to-end viewer smoke test (`tests/viewer_smoke.sh`). Spawns `rezolus view` in upload-only, file, A/B, and proxy modes, exercises the API endpoints, and verifies experiment attach/detach. Use after any change touching `src/viewer/` or before opening a viewer-related PR.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md3.4 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Viewer smoke test

Runs the viewer in four configurations against checked-in demo parquets and asserts the public API endpoints behave correctly. Designed to be invoked from a PR/commit hook so behavior regressions in src/viewer/ show up before review.

Steps

  1. Run the script:

    bash tests/viewer_smoke.sh
    
  2. Interpret the result:

    • Exit 0 → all assertions passed; viewer behaves correctly across upload-only, file mode, A/B compare mode, and proxy mode, including experiment attach/detach via the HTTP API.
    • Exit 1 → first failed assertion is printed, plus the failing viewer's startup log. Read both before guessing — the log usually says exactly what blew up (port collision, missing parquet, panic, etc.).
  3. If the script fails, do not paper over by editing the assertions. The script is the contract. If a behavioral change is intentional (e.g. a renamed JSON field), update the assertion in the same commit that changes the behavior, and call it out in the PR description.

What it covers

  • /api/v1/mode — loaded, compare_mode, url_loading flags across the four startup configs
  • /api/v1/sections — navigation list non-empty
  • /data/<section>.json — at least one group in the lazy-section payload
  • /api/v1/query_range — PromQL execution returns status:"success"
  • /api/v1/load_url — 403 envelope when proxy disabled, invalid_parquet envelope when fetching non-parquet bytes from an allowed host
  • POST /api/v1/captures/experiment — flips compare_mode:true
  • DELETE /api/v1/captures/experiment — flips compare_mode:false
  • Static assets — /, /about, /lib/style.css all return 200

What it does not cover

  • Live mode (rezolus view <agent-url>) — needs an actual rezolus agent listening, not reproducible without one.
  • Browser-rendered UI — the script only asserts on backend payload shape. For the rendered page, use the viewer-render skill: it drives a headless browser and asserts on geometry, computed colours, wrap points and console errors.
  • Compare-mode UI rendering — the experiment attach/detach assertion only checks the API flag flip; the rendered side-by-side view isn't exercised. Again viewer-render.

Requirements

  • cargo — builds the binary if it isn't already built
  • bash 4+, curl, jq — assertions
  • Ports 18500-18503 free
  • Internet access to httpbin.org for the proxy assertion (skipped with a warning if unreachable)

Triggering it from a hook

A typical wiring:

  • Per-PR (CI) — add a job to .github/workflows/cargo.yml that runs bash tests/viewer_smoke.sh after cargo build.
  • Per-commit (local) — .git/hooks/pre-push calling the same script. Slow (cold builds take ~60 s + 8 s of viewer warmup), so prefer the CI route unless the dev wants the early signal.
  • Per Claude Code session — invoke this skill via /viewer-smoke or have the agent call it from a SessionStart / PostToolUse hook that watches src/viewer/**.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Write or update the CLI `--help` text and README section for a new or changed rezolus feature (a subcommand, flag, mode, or behavior change), then prove the help is usable by dispatching a fresh subagent that has never seen the code. Use this whenever you add or change how rezolus is invoked — new `rezolus <subcommand>`, new flags/args on an existing mode, renamed options, or changed defaults — and any time the user says the help/README is thin, stale, confusing, or "an agent couldn't figure this out." Treats help text as an interface under test, not prose.

中文简介正在准备中。当前显示原文说明。

iopsystems/rezolus2772026年10月20日 更新

Use when starting or picking up a non-trivial effort (feature, investigation, perf probe, refactor, migration) in a shared repo where teammates or future agents must coordinate or hand off; when a repo has no durable in-tree record of decisions and dead-ends; when you're about to drop a well-measured negative result; or when bootstrapping a journal from a repo's commit history.

中文简介正在准备中。当前显示原文说明。

iopsystems/rezolus2772026年10月20日 更新

pr

免费

Create a feature branch, commit changes, push, and open a PR against iopsystems/rezolus

中文简介正在准备中。当前显示原文说明。

iopsystems/rezolus2772026年10月20日 更新

Tag and push a prerelease from the current Cargo.toml version. Use when the user wants to cut an alpha/beta/rc prerelease. Aborts on stable versions (no `-` in version string) and if the tag already exists.

中文简介正在准备中。当前显示原文说明。

iopsystems/rezolus2772026年10月20日 更新

release

免费

Create a release PR with version bump and changelog update

中文简介正在准备中。当前显示原文说明。

iopsystems/rezolus2772026年10月20日 更新

Use when reviewing a Rezolus sampler change before merge — a new sampler, a change to an existing sampler's probes/refresh/metrics, or core changes that affect samplers; or whenever a sampler's overhead, cadence, or data source is in question.

中文简介正在准备中。当前显示原文说明。

iopsystems/rezolus2772026年10月20日 更新

查看 iopsystems 的全部技能

报告此技能的问题