story-kit: create 65_story_standardised_script_test_entry_point_for_all_projects
This commit is contained in:
@@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
name: Standardised script/test Entry Point for All Projects
|
||||||
|
test_plan: pending
|
||||||
|
---
|
||||||
|
|
||||||
|
# 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
|
||||||
|
- [ ] For this project (story-kit-app), script/test runs cargo test, pnpm test, and pnpm test:e2e
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- TBD
|
||||||
Reference in New Issue
Block a user