Skip to content

Key first-run failures on Behavior to write #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
raghubetina merged 1 commit into from
Oct 12, 2026
Merged

Key first-run failures on Behavior to write #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions workshop-kit/scripts/linux/app-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,11 @@ except on testing, where the app's `AGENTS.md` and README govern.

## Setup and specs
- After Compile, set up the app, build its assets and run its specs as its README says, before the first preview.
In that first run, a `NotImplementedError` that names behavior listed under the README's **Behavior to write** is
work to do: write that behavior until its specs pass. If Chrome itself cannot start, this laptop's setup is
missing something; any other failure in that run is a First Draft defect. Either way, tell the user which spec
failed and its error. Never edit or delete a generated spec to make it pass.
In that first run, a spec that fails through behavior the README's **Behavior to write** lists is work to do:
write that behavior until its specs pass. A stub raises `NotImplementedError`, and a deletion outcome First Draft
left out fails its spec with `RecordNotDestroyed`. If Chrome itself cannot start, this laptop's setup is missing
something; any other failure in that run is a First Draft defect. Either way, tell the user which spec failed and
its error. Never edit or delete a generated spec to make it pass.
- System specs drive Chrome on this laptop directly; there is no Selenium container to start or stop.

## Web app
Expand Down