Skip to content
cccskills
FreePublished on GitHub

e2e-testing

E2E test conventions — semantic selectors, arrange-steps that prove the process started, runtime markers that cannot match the shell echo, and absolute-path tool invocations. Use when writing or changing a .feature scenario under packages/tests.

The English summary is being prepared. Showing the original description.

juspay/kolu
See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

E2E Tests

  • Use semantic selectors: Never match on CSS classes (class*="bg-...") in test selectors — classes are styling concerns and break when visual design changes. Use data-testid, data-active, or other semantic data-* attributes instead.

  • A step that starts a process must prove the process started. Typing a command into a PTY and waiting a frame is not an arrangement — it is an unconditional pass. Wait for a marker the process itself prints once it is up (e.g. from a listen callback), and on timeout quote the terminal's own last lines. Otherwise every environmental way the start can fail — EADDRINUSE from a leftover process, a missing tool, a shell still initializing — surfaces much later as a missing UI value and reads as a broken product. In #1982 that cost a CI cycle: the listener never started and the failure said "the Ports section showed []", pointing at the port sensor.

  • A marker you wait for must not appear literally in the command you type. The shell echoes the command line, so a waitForBufferContains("kolu-e2e-listening") matches the echo before the process runs — the same #1982 guard passed against /nonexistent/node. Build the marker at runtime ("kolu-e2e" + "-listening") so only the process's own output can satisfy it, and prove it: point the step at a broken binary and confirm it now fails at the start step, quoting the shell's own error. Any new wait/guard gets that negative test before you trust it.

  • Never depend on a tool being on the PTY's PATH. Run it by absolute path — process.execPath for node. A bare node resolves on every dev box and can fail only on a host where node lives solely in the dev shell, so the difference presents as a phantom product bug on one machine. Whether the shell resolves node is a different question from the one the scenario is asking.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

blog-post

Free

Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.

The English summary is being prepared. Showing the original description.

juspay/kolu82Updated Oct 21, 2026

ci

Free

Run this repo's CI end-to-end — kolu's policy on top of the odu runner: banned opt-out flags, x86_64-linux pinning, pool upkeep, fail-fast surfacing, e2e timing evidence, and the green-gate. Triggers on "run CI", "drive CI", "re-run the pipeline", "close the red check", "warm the pool". Runner mechanics live in the `/odu` skill.

The English summary is being prepared. Showing the original description.

juspay/kolu82Updated Oct 21, 2026

dev-server

Free

Launch the kolu dev server on two RANDOM free ports so it never collides with the running production `kolu.service`, remember the ports for the rest of the session, and tear down only the dev instance. Load before running the app locally — for evidence capture, driving a live kolu with the chrome-devtools MCP, or any `just dev` you'd otherwise run by hand. Triggers on "run kolu locally", "launch the dev server", "boot kolu", "drive a live kolu", "start the app to screenshot it", or before pointing chrome-devtools at a local kolu.

The English summary is being prepared. Showing the original description.

juspay/kolu82Updated Oct 21, 2026

diataxis

Free

Classify, write, and audit documentation per Diátaxis (diataxis.fr) — the four-quadrant method (tutorials · how-to guides · reference · explanation). Encodes the compass as a decision procedure, each quadrant's contract as hard rules, and an executable mixed-mode audit. Project-agnostic; the per-repo doc-location mapping lives in a repo rule of the project's own (kolu: the Kolu overlay below). Use when writing any user-facing doc, structuring a docs site, or auditing existing docs for mixed modes.

The English summary is being prepared. Showing the original description.

juspay/kolu82Updated Oct 21, 2026

dock-state

Free

The Dock's agent-state folds — one fenced source of truth in @kolu/terminal-vocab, the load-bearing order≠colour split, and the one "is something happening" question. Use when editing agentProjection or the canvas dock.

The English summary is being prepared. Showing the original description.

juspay/kolu82Updated Oct 21, 2026

evidence

Free

Produce visual PR evidence — a screenshot or video — whenever a change has on-screen impact. Tests are never a substitute; a change can be backend by cause and visible by effect. Capture via the project's e2e harness on a pu box, or by driving a live kolu with the chrome-devtools MCP; host on a GitHub release and post a `## Evidence` comment. Triggers on "post evidence", "screenshot the change", "record a video of this", "show it working", "prove it", or finishing any change whose effect is visible on screen.

The English summary is being prepared. Showing the original description.

juspay/kolu82Updated Oct 21, 2026

See all skills by juspay

Report a problem with this skill