Skip to content

Key first-run failures on Behavior to write #84

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 #84

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 .devcontainer/workshop/app-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,11 @@ Never print secrets, show a file that holds one, or ask the user to paste one in

## 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. Any other
failure in that run is a First Draft defect: tell the user which spec failed and its error. Never
edit or delete a generated spec to make it pass.
first preview. 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`. Any other failure in that run is a First Draft defect: tell the user which
spec failed and its error. Never edit or delete a generated spec to make it pass.
- System specs need a Selenium browser that this Codespace does not start by itself. From the app's
root, start it before every spec run (all specs, one spec file, or `bin/ci`) and stop it
afterward, even when specs fail. Run these lines as one command, with your spec command in place
Expand Down
Loading