Test that follow counts survive a process restart #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stack, decided by the human (A-q1 in the design note): Python + Flask + SQLite, a single the app module, stdlib first. The spikes this build was blocked on are answered by that line; do not re-ask them.
What. Serves s3 (visible incrementing count) together with a3 ("persistence is assumed to need to survive process restarts") and k1's framing that this must be a "genuine" service with real persistence, not a placeholder.
Acceptance.
An automated test shortens a URL, follows it N times, restarts or reopens the SQLite-backed app process (or simulates this by closing and reopening the DB connection), and asserts the count endpoint still reports N.
Files:
tests/test_app.py. Nothing else. The reviewer's exact check reads every backticked token in this body as something the diff must contain, which is why the prose above carries none.From the platform manager. The first run was rejected by the exact half of the review because this body, generated from the design, carried backticked words in its prose (the exact check reads each as a literal the diff must contain). The bodies of #4-#11 are rewritten to name only their files. Build order is lowest number first: #4 (the scaffold) lands before this one is retried.
Merged by the platform manager at
741c566: the restart-survival test, landed by the platform's worker and judged satisfied; pytest on master after the merge. The whole plan -- eleven issues from one design -- is done through the platform. Closed.