Test Report

Throw Joshua Under The Bus · Thu, 19 Feb 2026 09:25:04 GMT
Commit 45a7525

117

Total Tests

117

Passed

Failed

Not Covered

Passed 117

Unit Tests 22/22

Positive 19/19

✓ F1.R1 counter file created on startup if missing 290ms

✓ F1.R2 counter file contains valid JSON with count key 228ms

✓ F2.R1 count is a non-negative integer 229ms

✓ F2.R1 initialized counter starts at zero 232ms

✓ F3.R1 atomic writes use tmp + rename pattern 228ms

✓ F3.R2 backup recovery on corrupt file 261ms

✓ F3.R1 backup file is written alongside main file 231ms

✓ F26.R1 feature request saved to disk 285ms

✓ F26.R1 readFeatureRequests returns saved data 229ms

✓ F26.R2 feature request has id, text, and timestamp 156ms

✓ F26.R2 multiple feature requests preserved in order 163ms

✓ F26.R2 feature request uses atomic write (tmp + rename) 160ms

✓ F29.R1 activeUsers map exists and is a Map 216ms

✓ F29.R1 trackUser adds an entry to activeUsers 2ms

✓ F29.R1 trackUser updates lastSeen on repeated calls 1ms

✓ F29.R2 getActiveUserCount returns correct count for active users 1ms

✓ F29.R2 getActiveUserCount returns 0 when no users tracked 0ms

✓ F29.R2 getActiveUserCount excludes stale entries beyond ACTIVE_USER_WINDOW 1ms

✓ F29.R2 getActiveUserCount counts unique IPs only 1ms

Negative 3/3

✓ F3.R2 returns count 0 when both main and backup are missing 232ms

✓ F3.R2 returns count 0 when main is corrupt and backup is also corrupt 258ms

✓ F26.R1 readFeatureRequests returns empty array when file missing 228ms

Integration Tests 49/49

Positive 40/40

✓ F25.R1 POST /api/admin/login with correct credentials succeeds 198ms

✓ F25.R2 GET /api/admin/status returns { authenticated: false } when not logged in 169ms

✓ F25.R2 GET /api/admin/status returns { authenticated: true } when logged in 172ms

✓ F25.R3 POST /api/admin/toggle-action disables throw 178ms

✓ F25.R3 disabled throw returns 403 from POST /api/increment 187ms

✓ F25.R3 disabled guard returns 403 from POST /api/guard 178ms

✓ F25.R3 disabled ambulance returns 403 from POST /api/ambulance 168ms

✓ F25.R3 re-enabling action allows it again 181ms

✓ F25.R3 GET /api/counter includes disabledActions with throw, guard, ambulance 166ms

✓ F15.R1 returns 200 with { count } 212ms

✓ F15.R2 Content-Type is application/json 162ms

✓ F15.R2 body has count and guards fields 181ms

✓ F15.R3 count is a non-negative integer 167ms

✓ F15.R4 reflects count after increments 171ms

✓ F16.R1 increments counter by 1 169ms

✓ F16.R2 returns { count, guards } 187ms

✓ F16.R3 count incremented by 1 172ms

✓ F16.R4 increment persists to disk 251ms

✓ F16.R4 counter starts at 0 246ms

✓ F16.R5 does not require bodyPart field 272ms

✓ F16.R5 succeeds with no request body at all 273ms

✓ F20.R1 adds a guard and returns updated state 223ms

✓ F20.R1 guards accumulate on multiple calls 188ms

✓ F20.R5 throw with active guards consumes a guard instead of incrementing count 183ms

✓ F20.R5 increments count when no guards remain 188ms

✓ F20.R2 guards cannot exceed 10 182ms

✓ F20.R2 guards cap at max 10 from zero 206ms

✓ F20.R3 GET /api/counter reflects decayed guards 188ms

✓ F20.R3 guards decay to zero when enough time passes 181ms

✓ F26.R1 returns empty array when no requests exist 227ms

✓ F26.R1 returns previously submitted requests 196ms

✓ F26.R1 response Content-Type is application/json 199ms

✓ F26.R2 creates a new feature request 183ms

✓ F26.R2 persists request to feature-requests.json file 189ms

✓ F26.R2 trims whitespace from request text 187ms

✓ F21.R1 decrements counter by 1 235ms

✓ F21.R1 returns count and guards in response 196ms

✓ F21.R2 429 response includes retryAfter as a number 195ms

✓ F21.R3 cannot go below 0 192ms

✓ F21.R3 decrementing from 1 results in 0, not negative 196ms

Negative 9/9

✓ F25.R1 POST /api/admin/login with bad credentials returns 401 428ms

✓ F25.R1 POST /api/admin/login with wrong username returns 401 181ms

✓ F25.R1 POST /api/admin/login with missing fields returns 400 198ms

✓ F25.R3 POST /api/admin/toggle-action rejects invalid action 212ms

✓ F25.R3 POST /api/admin/toggle-action requires auth 163ms

✓ F16.R3 returns 429 after exceeding rate limit 500ms

✓ F26.R2 rejects empty text 191ms

✓ F26.R2 rejects missing text field 197ms

✓ F21.R2 returns 429 on cooldown 202ms

Contract Tests 28/28

Positive 23/23

✓ F15.R2 returns 200 with application/json content-type 210ms

✓ F15.R1 response body has count as a number 163ms

✓ F15.R1 response body has guards as a number 174ms

✓ F15.R1 response body has users as a number 173ms

✓ F15.R1 response body has disabledActions object 168ms

✓ F15.R1 count is a non-negative integer 170ms

✓ F15.R1 does not include bodyPartHits or shields fields 195ms

✓ F16.R2 returns 200 with application/json content-type 231ms

✓ F16.R2 response body has count and guards fields 289ms

✓ F16.R2 count is a positive integer after increment from zero 507ms

✓ F16.R2 does not include bodyPartHits or shields fields 163ms

✓ F16.R2 no bodyPart field required in request 166ms

✓ F26.R1 returns 200 with application/json content-type 220ms

✓ F26.R1 response body is an array 170ms

✓ F26.R1 empty array when no feature requests exist 180ms

✓ F26.R2 returns 201 with valid text 177ms

✓ F26.R2 response body has id, text, timestamp, implemented fields 189ms

✓ F26.R2 created request appears in subsequent GET 186ms

✓ F14.R1 returns 200 with text/html content-type 226ms

✓ F14.R2 HTML contains "Throw Joshua Under The Bus" 179ms

✓ F19.R2 GET /features redirects to /features/ 179ms

✓ F19.R3 GET /style.css returns CSS content-type 188ms

✓ F19.R4 GET /script.js returns JavaScript content-type 182ms

Negative 5/5

✓ F15.R1 POST /api/counter is not allowed 158ms

✓ F16.R2 GET /api/increment is not allowed 162ms

✓ F26.R2 returns 400 when text is missing 184ms

✓ F26.R2 returns 400 when text is empty string 182ms

✓ F19.R1 GET /nonexistent-file.xyz returns 404 186ms

Functional Tests 18/18

✓ F21.R1 Ambulance button is visible 264ms

✓ F21.R2 Ambulance button shows cooldown after use 913ms

✓ F7.R1 Page loads with counter display visible 185ms

✓ F7.R2 Counter shows a number 191ms

✓ F8.R1 Joshua doll SVG is visible 207ms

✓ F9.R1 Clicking Joshua triggers throw 234ms

✓ F10.R1 Counter increments after throw 726ms

✓ F26.R1 Feature request form is visible on /feature-requests/ 158ms

✓ F26.R2 Submitting a feature request works 1.7s

✓ F20.R1 Guard button is visible 194ms

✓ F20.R2 Clicking guard adds guards 350ms

✓ F20.R3 Guard display shows count 575ms

✓ F14.R1 Homepage has title "Throw Joshua Under The Bus" 213ms

✓ F14.R2 Page has nav tabs visible 152ms

✓ F19.R1 Features page accessible at /features/ 187ms

✓ F19.R2 Releases page accessible at /releases/ 154ms

✓ F19.R3 Feature requests page accessible at /feature-requests/ 147ms

✓ F19.R4 Admin page accessible at /admin/ 124ms

Requirement Coverage 38/99 (38%)

F1 Counter display

2/3 reqs

F1.R1 Counter element is visible on page load ✓

✓ Unit positive counter file created on startup if missing 290ms

F1.R2 Counter shows a numeric value ✓

✓ Unit positive counter file contains valid JSON with count key 228ms

F1.R3 Displayed value matches API response NOT COVERED

F2 Counter increment (throw)

1/3 reqs

F2.R1 Click sends POST /api/increment ✓

✓ Unit positive count is a non-negative integer 229ms

✓ Unit positive initialized counter starts at zero 232ms

F2.R2 Display updates to new count after click NOT COVERED

F2.R3 Multiple sequential clicks increment correctly NOT COVERED

F3 Counter persistence

2/4 reqs

F3.R1 Value written to counter.json on increment ✓

✓ Unit positive atomic writes use tmp + rename pattern 228ms

✓ Unit positive backup file is written alongside main file 231ms

F3.R2 Counter file created on init if missing ✓

✓ Unit positive backup recovery on corrupt file 261ms

✓ Unit negative returns count 0 when both main and backup are missing 232ms

✓ Unit negative returns count 0 when main is corrupt and backup is also corrupt 258ms

F3.R3 Existing counter file not overwritten on init NOT COVERED

F3.R4 Write handles zero, negative, and large numbers NOT COVERED

F4 Multi-user sync

0/2 reqs

F4.R1 Polls GET /api/counter every 5 seconds NOT COVERED

F4.R2 Display updates when server value changes externally NOT COVERED

F5 Double-click protection

0/2 reqs

F5.R1 isUpdating lock prevents concurrent submits NOT COVERED

F5.R2 Rapid clicking results in only one increment NOT COVERED

F6 Number formatting

0/1 reqs

F6.R1 Uses toLocaleString for thousands separators NOT COVERED

F7 Joshua doll SVG

2/2 reqs

F7.R1 SVG element is visible with nonzero dimensions ✓

✓ Functional positive Page loads with counter display visible 185ms

F7.R2 SVG has role="img" and aria-label ✓

✓ Functional positive Counter shows a number 191ms

F8 Bus animation

1/2 reqs

F8.R1 Bus SVG animates across screen on throw ✓

✓ Functional positive Joshua doll SVG is visible 207ms

F8.R2 Bus animation completes and resets NOT COVERED

F9 Counter bump animation

1/1 reqs

F9.R1 .bump class fires on counter after increment ✓

✓ Functional positive Clicking Joshua triggers throw 234ms

F10 Toast notifications

1/4 reqs

F10.R1 Toast becomes visible on error ✓

✓ Functional positive Counter increments after throw 726ms

F10.R2 Toast shows descriptive error message NOT COVERED

F10.R3 Toast auto-dismisses after 4 seconds NOT COVERED

F10.R4 Toast has error styling class NOT COVERED

F11 Error recovery UI

0/2 reqs

F11.R1 Counter shows "Error" on load failure NOT COVERED

F11.R2 .error-message div appended with unable-to-connect text NOT COVERED

F12 Responsive design

0/2 reqs

F12.R1 Layout adapts at 600px breakpoint NOT COVERED

F12.R2 Joshua doll smaller on mobile NOT COVERED

F13 Accessibility

0/5 reqs

F13.R1 Throw button has aria-label NOT COVERED

F13.R2 SVG has role="img" and aria-label NOT COVERED

F13.R3 Toast has aria-live="polite" NOT COVERED

F13.R4 Button has focus-visible ring NOT COVERED

F13.R5 Button activatable via keyboard NOT COVERED

F14 Homepage HTML

2/2 reqs

F14.R1 GET / returns 200 with HTML ✓

✓ Contract positive returns 200 with text/html content-type 226ms

✓ Functional positive Homepage has title "Throw Joshua Under The Bus" 213ms

F14.R2 Contains #counter-value, #throw-button, title ✓

✓ Contract positive HTML contains "Throw Joshua Under The Bus" 179ms

✓ Functional positive Page has nav tabs visible 152ms

F15 GET /api/counter

4/4 reqs

F15.R1 Returns 200 with application/json ✓

✓ Contract positive response body has count as a number 163ms

✓ Contract positive response body has guards as a number 174ms

✓ Contract positive response body has users as a number 173ms

✓ Contract positive response body has disabledActions object 168ms

✓ Contract positive count is a non-negative integer 170ms

✓ Contract positive does not include bodyPartHits or shields fields 195ms

✓ Contract negative POST /api/counter is not allowed 158ms

✓ Integration positive returns 200 with { count } 212ms

F15.R2 Body has count and guards fields ✓

✓ Contract positive returns 200 with application/json content-type 210ms

✓ Integration positive Content-Type is application/json 162ms

✓ Integration positive body has count and guards fields 181ms

F15.R3 count is a non-negative integer ✓

✓ Integration positive count is a non-negative integer 167ms

F15.R4 Reflects count after increments ✓

✓ Integration positive reflects count after increments 171ms

F16 POST /api/increment

5/5 reqs

F16.R1 Returns 200 with application/json ✓

✓ Integration positive increments counter by 1 169ms

F16.R2 Body has count and guards fields ✓

✓ Contract positive returns 200 with application/json content-type 231ms

✓ Contract positive response body has count and guards fields 289ms

✓ Contract positive count is a positive integer after increment from zero 507ms

✓ Contract positive does not include bodyPartHits or shields fields 163ms

✓ Contract positive no bodyPart field required in request 166ms

✓ Contract negative GET /api/increment is not allowed 162ms

✓ Integration positive returns { count, guards } 187ms

F16.R3 count incremented by 1 ✓

✓ Integration positive count incremented by 1 172ms

✓ Integration negative returns 429 after exceeding rate limit 500ms

F16.R4 Increment persists to disk ✓

✓ Integration positive increment persists to disk 251ms

✓ Integration positive counter starts at 0 246ms

F16.R5 No bodyPart field required ✓

✓ Integration positive does not require bodyPart field 272ms

✓ Integration positive succeeds with no request body at all 273ms

F17 Counter file recovery

0/3 reqs

F17.R1 Returns { count: 0 } when file missing NOT COVERED

F17.R2 Recreates file when missing NOT COVERED

F17.R3 Returns { count: 0 } for invalid JSON NOT COVERED

F18 CORS

0/2 reqs

F18.R1 Access-Control-Allow-Origin: * on GET NOT COVERED

F18.R2 CORS headers on POST NOT COVERED

F19 Static file serving

3/3 reqs

F19.R1 CSS and JS load successfully ✓

✓ Contract negative GET /nonexistent-file.xyz returns 404 186ms

✓ Functional positive Features page accessible at /features/ 187ms

F19.R2 Favicon link element exists ✓

✓ Contract positive GET /features redirects to /features/ 179ms

✓ Functional positive Releases page accessible at /releases/ 154ms

F19.R3 404 for nonexistent assets ✓

✓ Contract positive GET /style.css returns CSS content-type 188ms

✓ Functional positive Feature requests page accessible at /feature-requests/ 147ms

F20 Crossing Guard

4/7 reqs

F20.R1 Guard button visible on page ✓

✓ Integration positive adds a guard and returns updated state 223ms

✓ Integration positive guards accumulate on multiple calls 188ms

✓ Functional positive Guard button is visible 194ms

F20.R2 Click sends POST /api/guard ✓

✓ Integration positive guards cannot exceed 10 182ms

✓ Integration positive guards cap at max 10 from zero 206ms

✓ Functional positive Clicking guard adds guards 350ms

F20.R3 Guard count displayed ✓

✓ Integration positive GET /api/counter reflects decayed guards 188ms

✓ Integration positive guards decay to zero when enough time passes 181ms

✓ Functional positive Guard display shows count 575ms

F20.R4 Guard animation on click NOT COVERED

F20.R5 Throw with active guards consumes a guard instead ✓

✓ Integration positive throw with active guards consumes a guard instead of incrementing count 183ms

✓ Integration positive increments count when no guards remain 188ms

F20.R6 Guards decay by 1 every 10 seconds (server-side) NOT COVERED

F20.R7 Guard maximum is 10 NOT COVERED

F21 Ambulance (heal)

3/6 reqs

F21.R1 Ambulance button visible on page ✓

✓ Integration positive decrements counter by 1 235ms

✓ Integration positive returns count and guards in response 196ms

✓ Functional positive Ambulance button is visible 264ms

F21.R2 Click sends POST /api/ambulance ✓

✓ Integration negative returns 429 on cooldown 202ms

✓ Integration positive 429 response includes retryAfter as a number 195ms

✓ Functional positive Ambulance button shows cooldown after use 913ms

F21.R3 Ambulance decrements counter (minimum 0) ✓

✓ Integration positive cannot go below 0 192ms

✓ Integration positive decrementing from 1 results in 0, not negative 196ms

F21.R4 Ambulance animation on click NOT COVERED

F21.R5 Ambulance has 3-second cooldown per user NOT COVERED

F21.R6 Cooldown timer displayed near ambulance button NOT COVERED

F22 Current Users Display

0/4 reqs

F22.R1 Current user count displayed on page NOT COVERED

F22.R2 Count updates on poll NOT COVERED

F22.R3 Server tracks users by IP with 15s window NOT COVERED

F22.R4 GET /api/users returns users grouped by location NOT COVERED

F23 Rate Limiting

0/2 reqs

F23.R1 Rate limiter middleware applied to /api/* routes NOT COVERED

F23.R2 429 response returned when limit exceeded NOT COVERED

F24 Server-Side Ambulance Cooldown

0/3 reqs

F24.R1 Server tracks ambulance cooldown per IP NOT COVERED

F24.R2 Ambulance rejected with 429 when on cooldown NOT COVERED

F24.R3 First ambulance succeeds, immediate second is rejected NOT COVERED

F25 WebSocket Sync

3/3 reqs

F25.R1 WebSocket server attached to HTTP server ✓

✓ Integration negative POST /api/admin/login with bad credentials returns 401 428ms

✓ Integration negative POST /api/admin/login with wrong username returns 401 181ms

✓ Integration negative POST /api/admin/login with missing fields returns 400 198ms

✓ Integration positive POST /api/admin/login with correct credentials succeeds 198ms

F25.R2 State broadcast on every mutation ✓

✓ Integration positive GET /api/admin/status returns { authenticated: false } when not logged in 169ms

✓ Integration positive GET /api/admin/status returns { authenticated: true } when logged in 172ms

F25.R3 Client receives initial state on WebSocket connect ✓

✓ Integration positive POST /api/admin/toggle-action disables throw 178ms

✓ Integration positive disabled throw returns 403 from POST /api/increment 187ms

✓ Integration positive disabled guard returns 403 from POST /api/guard 178ms

✓ Integration positive disabled ambulance returns 403 from POST /api/ambulance 168ms

✓ Integration positive re-enabling action allows it again 181ms

✓ Integration negative POST /api/admin/toggle-action rejects invalid action 212ms

✓ Integration negative POST /api/admin/toggle-action requires auth 163ms

✓ Integration positive GET /api/counter includes disabledActions with throw, guard, ambulance 166ms

F26 Atomic File Writes

2/2 reqs

F26.R1 writeState uses tmp file + rename pattern ✓

✓ Unit positive feature request saved to disk 285ms

✓ Unit positive readFeatureRequests returns saved data 229ms

✓ Unit negative readFeatureRequests returns empty array when file missing 228ms

✓ Contract positive returns 200 with application/json content-type 220ms

✓ Contract positive response body is an array 170ms

✓ Contract positive empty array when no feature requests exist 180ms

✓ Integration positive returns empty array when no requests exist 227ms

✓ Integration positive returns previously submitted requests 196ms

✓ Integration positive response Content-Type is application/json 199ms

✓ Functional positive Feature request form is visible on /feature-requests/ 158ms

F26.R2 No .tmp file remains after successful write ✓

✓ Unit positive feature request has id, text, and timestamp 156ms

✓ Unit positive multiple feature requests preserved in order 163ms

✓ Unit positive feature request uses atomic write (tmp + rename) 160ms

✓ Contract positive returns 201 with valid text 177ms

✓ Contract positive response body has id, text, timestamp, implemented fields 189ms

✓ Contract positive created request appears in subsequent GET 186ms

✓ Contract negative returns 400 when text is missing 184ms

✓ Contract negative returns 400 when text is empty string 182ms

✓ Integration positive creates a new feature request 183ms

✓ Integration positive persists request to feature-requests.json file 189ms

✓ Integration negative rejects empty text 191ms

✓ Integration negative rejects missing text field 197ms

✓ Integration positive trims whitespace from request text 187ms

✓ Functional positive Submitting a feature request works 1.7s

F27 Progressive Web App (PWA)

0/4 reqs

F27.R1 Web app manifest served at /manifest.json NOT COVERED

F27.R2 Manifest has required PWA fields NOT COVERED

F27.R3 Service worker registered on page load NOT COVERED

F27.R4 HTML includes PWA meta tags NOT COVERED

F28 Versioning & Navigation

0/3 reqs

F28.R1 Version number displayed on page NOT COVERED

F28.R2 Version number links to /releases/ page NOT COVERED

F28.R3 Version.json endpoint provides current version NOT COVERED

F29 User Feature Requests

2/3 reqs

F29.R1 Feature Requests page with form and request history ✓

✓ Unit positive activeUsers map exists and is a Map 216ms

✓ Unit positive trackUser adds an entry to activeUsers 2ms

✓ Unit positive trackUser updates lastSeen on repeated calls 1ms

F29.R2 Server-side persistence shared across all users ✓

✓ Unit positive getActiveUserCount returns correct count for active users 1ms

✓ Unit positive getActiveUserCount returns 0 when no users tracked 0ms

✓ Unit positive getActiveUserCount excludes stale entries beyond ACTIVE_USER_WINDOW 1ms

✓ Unit positive getActiveUserCount counts unique IPs only 1ms

F29.R3 Implemented requests marked with release version link NOT COVERED

F30 Admin Panel

0/4 reqs

F30.R1 Admin authentication with login/logout NOT COVERED

F30.R2 Counter management (reset and set) NOT COVERED

F30.R3 Action toggle (disable/enable throw, guard, ambulance) NOT COVERED

F30.R4 Approve or deny feature requests NOT COVERED

F31 Security Headers

0/2 reqs

F31.R1 Security headers middleware on all responses NOT COVERED

F31.R2 CSP allows only same-origin and inline resources NOT COVERED

F32 CI/CD Pipeline

0/1 reqs

F32.R1 Automated test, deploy, verify jobs NOT COVERED

F33 Automated Feature Implementation

0/3 reqs

F33.R1 Polling script detects approved feature requests NOT COVERED

F33.R2 Claude Code launched headlessly to implement features NOT COVERED

F33.R3 Mark-implemented workflow notifies production server NOT COVERED

v1.0.0.0 — Initial Release (2026-02-18) 117/117

✓ F25.R1 POST /api/admin/login with bad credentials returns 401 428ms

✓ F25.R1 POST /api/admin/login with wrong username returns 401 181ms

✓ F25.R1 POST /api/admin/login with missing fields returns 400 198ms

✓ F25.R1 POST /api/admin/login with correct credentials succeeds 198ms

✓ F25.R2 GET /api/admin/status returns { authenticated: false } when not logged in 169ms

✓ F25.R2 GET /api/admin/status returns { authenticated: true } when logged in 172ms

✓ F25.R3 POST /api/admin/toggle-action disables throw 178ms

✓ F25.R3 disabled throw returns 403 from POST /api/increment 187ms

✓ F25.R3 disabled guard returns 403 from POST /api/guard 178ms

✓ F25.R3 disabled ambulance returns 403 from POST /api/ambulance 168ms

✓ F25.R3 re-enabling action allows it again 181ms

✓ F25.R3 POST /api/admin/toggle-action rejects invalid action 212ms

✓ F25.R3 POST /api/admin/toggle-action requires auth 163ms

✓ F25.R3 GET /api/counter includes disabledActions with throw, guard, ambulance 166ms

✓ F15.R2 returns 200 with application/json content-type 210ms

✓ F15.R1 response body has count as a number 163ms

✓ F15.R1 response body has guards as a number 174ms

✓ F15.R1 response body has users as a number 173ms

✓ F15.R1 response body has disabledActions object 168ms

✓ F15.R1 count is a non-negative integer 170ms

✓ F15.R1 does not include bodyPartHits or shields fields 195ms

✓ F16.R2 returns 200 with application/json content-type 231ms

✓ F16.R2 response body has count and guards fields 289ms

✓ F16.R2 count is a positive integer after increment from zero 507ms

✓ F16.R2 does not include bodyPartHits or shields fields 163ms

✓ F16.R2 no bodyPart field required in request 166ms

✓ F15.R1 POST /api/counter is not allowed 158ms

✓ F16.R2 GET /api/increment is not allowed 162ms

✓ F15.R1 returns 200 with { count } 212ms

✓ F15.R2 Content-Type is application/json 162ms

✓ F15.R2 body has count and guards fields 181ms

✓ F15.R3 count is a non-negative integer 167ms

✓ F15.R4 reflects count after increments 171ms

✓ F16.R1 increments counter by 1 169ms

✓ F16.R2 returns { count, guards } 187ms

✓ F16.R3 count incremented by 1 172ms

✓ F16.R4 increment persists to disk 251ms

✓ F16.R4 counter starts at 0 246ms

✓ F16.R5 does not require bodyPart field 272ms

✓ F16.R5 succeeds with no request body at all 273ms

✓ F16.R3 returns 429 after exceeding rate limit 500ms

✓ F1.R1 counter file created on startup if missing 290ms

✓ F1.R2 counter file contains valid JSON with count key 228ms

✓ F2.R1 count is a non-negative integer 229ms

✓ F2.R1 initialized counter starts at zero 232ms

✓ F3.R1 atomic writes use tmp + rename pattern 228ms

✓ F3.R2 backup recovery on corrupt file 261ms

✓ F3.R2 returns count 0 when both main and backup are missing 232ms

✓ F3.R2 returns count 0 when main is corrupt and backup is also corrupt 258ms

✓ F3.R1 backup file is written alongside main file 231ms

✓ F26.R1 feature request saved to disk 285ms

✓ F26.R1 readFeatureRequests returns saved data 229ms

✓ F26.R1 readFeatureRequests returns empty array when file missing 228ms

✓ F26.R2 feature request has id, text, and timestamp 156ms

✓ F26.R2 multiple feature requests preserved in order 163ms

✓ F26.R2 feature request uses atomic write (tmp + rename) 160ms

✓ F26.R1 returns 200 with application/json content-type 220ms

✓ F26.R1 response body is an array 170ms

✓ F26.R1 empty array when no feature requests exist 180ms

✓ F26.R2 returns 201 with valid text 177ms

✓ F26.R2 response body has id, text, timestamp, implemented fields 189ms

✓ F26.R2 created request appears in subsequent GET 186ms

✓ F26.R2 returns 400 when text is missing 184ms

✓ F26.R2 returns 400 when text is empty string 182ms

✓ F20.R1 adds a guard and returns updated state 223ms

✓ F20.R1 guards accumulate on multiple calls 188ms

✓ F20.R5 throw with active guards consumes a guard instead of incrementing count 183ms

✓ F20.R5 increments count when no guards remain 188ms

✓ F20.R2 guards cannot exceed 10 182ms

✓ F20.R2 guards cap at max 10 from zero 206ms

✓ F20.R3 GET /api/counter reflects decayed guards 188ms

✓ F20.R3 guards decay to zero when enough time passes 181ms

✓ F26.R1 returns empty array when no requests exist 227ms

✓ F26.R1 returns previously submitted requests 196ms

✓ F26.R1 response Content-Type is application/json 199ms

✓ F26.R2 creates a new feature request 183ms

✓ F26.R2 persists request to feature-requests.json file 189ms

✓ F26.R2 rejects empty text 191ms

✓ F26.R2 rejects missing text field 197ms

✓ F26.R2 trims whitespace from request text 187ms

✓ F14.R1 returns 200 with text/html content-type 226ms

✓ F14.R2 HTML contains "Throw Joshua Under The Bus" 179ms

✓ F19.R2 GET /features redirects to /features/ 179ms

✓ F19.R3 GET /style.css returns CSS content-type 188ms

✓ F19.R4 GET /script.js returns JavaScript content-type 182ms

✓ F19.R1 GET /nonexistent-file.xyz returns 404 186ms

✓ F29.R1 activeUsers map exists and is a Map 216ms

✓ F29.R1 trackUser adds an entry to activeUsers 2ms

✓ F29.R1 trackUser updates lastSeen on repeated calls 1ms

✓ F29.R2 getActiveUserCount returns correct count for active users 1ms

✓ F29.R2 getActiveUserCount returns 0 when no users tracked 0ms

✓ F29.R2 getActiveUserCount excludes stale entries beyond ACTIVE_USER_WINDOW 1ms

✓ F29.R2 getActiveUserCount counts unique IPs only 1ms

✓ F21.R1 decrements counter by 1 235ms

✓ F21.R1 returns count and guards in response 196ms

✓ F21.R2 returns 429 on cooldown 202ms

✓ F21.R2 429 response includes retryAfter as a number 195ms

✓ F21.R3 cannot go below 0 192ms

✓ F21.R3 decrementing from 1 results in 0, not negative 196ms

✓ F21.R1 Ambulance button is visible 264ms

✓ F21.R2 Ambulance button shows cooldown after use 913ms

✓ F7.R1 Page loads with counter display visible 185ms

✓ F7.R2 Counter shows a number 191ms

✓ F8.R1 Joshua doll SVG is visible 207ms

✓ F9.R1 Clicking Joshua triggers throw 234ms

✓ F10.R1 Counter increments after throw 726ms

✓ F26.R1 Feature request form is visible on /feature-requests/ 158ms

✓ F26.R2 Submitting a feature request works 1.7s

✓ F20.R1 Guard button is visible 194ms

✓ F20.R2 Clicking guard adds guards 350ms

✓ F20.R3 Guard display shows count 575ms

✓ F14.R1 Homepage has title "Throw Joshua Under The Bus" 213ms

✓ F14.R2 Page has nav tabs visible 152ms

✓ F19.R1 Features page accessible at /features/ 187ms

✓ F19.R2 Releases page accessible at /releases/ 154ms

✓ F19.R3 Feature requests page accessible at /feature-requests/ 147ms

✓ F19.R4 Admin page accessible at /admin/ 124ms

All tests passed