story-kit: accept 65_story_standardised_script_test_entry_point_for_all_projects
This commit is contained in:
@@ -1,24 +0,0 @@
|
||||
---
|
||||
name: Standardised script/test Entry Point for All Projects
|
||||
test_plan: approved
|
||||
---
|
||||
|
||||
# Story 65: Standardised script/test Entry Point for All Projects
|
||||
|
||||
## User Story
|
||||
|
||||
As a Story Kit user, I want every project initialised by Story Kit to have a script/ directory with a test script, so that agents and the system always have a known location to run all tests (including e2e) without needing to know project-specific commands.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] 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 — 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
|
||||
|
||||
- Other script/ entry points (script/setup, script/lint, etc) — future stories
|
||||
- Changing how individual test frameworks work
|
||||
Reference in New Issue
Block a user