From 4f74947cb98d2104110e9a220eeabfe547d2233f Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 12:26:01 +0000 Subject: [PATCH] story-kit: create 65_story_standardised_script_test_entry_point_for_all_projects --- ...standardised_script_test_entry_point_for_all_projects.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md b/.story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md index c9f0a21..24dd69a 100644 --- a/.story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md +++ b/.story_kit/work/1_upcoming/65_story_standardised_script_test_entry_point_for_all_projects.md @@ -14,9 +14,11 @@ As a Story Kit user, I want every project initialised by Story Kit to have a scr - [ ] Story Kit project scaffolding creates a script/ directory in the project root - [ ] A script/test executable is created during init with a sensible default (e.g. exit 0 or echo no tests configured) - [ ] The Rust server can invoke script/test as the canonical way to run all tests for any project -- [ ] Agents use script/test instead of guessing test commands +- [ ] Agents use script/test instead of guessing test commands — they only need to check output if exit code is non-zero, saving LLM tokens +- [ ] script/test exits 0 on success, non-zero on failure — agents treat it as a single pass/fail gate without parsing output on success - [ ] For this project (story-kit-app), script/test runs cargo test, pnpm test, and pnpm test:e2e ## Out of Scope -- TBD +- Other script/ entry points (script/setup, script/lint, etc) — future stories +- Changing how individual test frameworks work