# BF-TC-003: design capacity-boundary checks

**Design status:** Learner-authored sequential boundary plan from supplied goal, reviewed with corrected negative fixture and expected result. **Execution:** Pass. **Run:** BF-RUN-005. **Requirements:** BF-REQ-05; BF-REQ-07; BF-REQ-12. **Review/execution date:** 2026-10-15.

Studio A permits whole-number party sizes from **1 to 8**, inclusive. A valid 8-person booking should save; an otherwise valid 9-person booking should be rejected. Rejection of invalid input is a passing negative-test checkpoint.

## Learner proposal and review

The learner specified reset release 1.1, Alex Rivera / Practice123, Test01 in Studio A on 2026-11-17 at 12:00 for 60 minutes and 8 people, followed by test02 in Studio A on 2026-11-18 at 13:00 for 60 minutes and 9 people, then before/after-refresh screenshots. Their proposed expectation was that both bookings would be created without issues.

Coached corrections:

- Studio A's 8-person maximum means the second booking must be rejected, not created.
- November 18 is closed. Using it would introduce a second invalid condition and could trigger date feedback before capacity is evaluated.
- Move the second attempt to **November 17 at 14:00 for 60 minutes**. Studio A is free then after reset and the first Test01 booking; Alex's sample 14:00 booking is in Studio B. This also avoids touching the first booking's 13:00 end.

The learner supplied the detailed sequence, titles, account, first fixture, 8/9 input pair, and refresh idea. The coach supplied the corrected second fixture, rejection expectation, and evidence checkpoints. This is reviewed learner work, not fully independent expectation design.

## Reviewed execution plan

1. Select 1.1 and reset the release to restore sample data.
2. Sign in as Alex Rivera — customer using Practice123.
3. Create **Test01**, Studio A, **2026-11-17**, **12:00**, **60 minutes**, **8 people**.
4. Capture creation feedback and saved BF-003 details.
5. Fill **test02**, Studio A, **2026-11-17**, **14:00**, **60 minutes**, **9 people**. Explicitly fill the form again because valid creation resets its values.
6. Select Create booking and capture validation feedback plus the unchanged saved list.
7. Refresh and capture the saved list again with Show status All.

Expected at the first checkpoint: Test01 saves as BF-003, Confirmed, Studio A, 2026-11-17, 12:00–13:00, 8 people. Alex has two saved bookings including sample BF-002.

Expected at the second checkpoint: useful feedback explains the 1–8 whole-number capacity; no test02 record is created; BF-003 and BF-002 remain unchanged. The rejected form values remain available for correction before refresh.

Expected after refresh: the two saved bookings retain their details; test02 remains absent. Temporary errors and unsaved form values need not persist. A different rejection reason should be investigated against setup rather than automatically counted as proof of correct capacity validation.

Overall verdict can be Pass only when the valid maximum, invalid above-maximum, and refresh checkpoints are complete. Partial observations are In progress. This combined sequence is one planned execution with several checkpoints, not two additional completed runs.

## Observed results and verdict

The learner reports that the first booking succeeded, the second was rejected for exceeding the eight-person maximum, and the saved first booking remained after refresh. Three images show Alex Rivera / Customer / release 1.1 and All status:

| Checkpoint | Observed result | Verdict |
| --- | --- | --- |
| At maximum | Test01 saved as BF-003, Confirmed, Studio A, 2026-11-17, 12:00–13:00, 8 people; creation feedback shown. | Pass |
| Above maximum | Actual draft title Test02 (capital T), Studio A, 2026-11-17, 14:00, 60 minutes, 9 people; feedback: “Enter a whole number from 1 to 8 for Studio A.” Draft values retained; two saved bookings remain. | Pass |
| Refresh | BF-002 and BF-003 retain all shown details; count remains 2 shown / 2 total; no Test02 saved. Form resets and temporary feedback clears as permitted. | Pass |

Overall verdict: **Pass** for the combined BF-RUN-005. It adds one execution and the third executed reviewed learner-authored case. No new defect is claimed. This verifies Studio A's upper boundary in this fixture; other capacities, lower boundaries, and invalid number formats remain separate coverage.

Evidence:

- [Eight accepted](../evidence/session-03/BF-RUN-005_v1.1_capacity-eight-accepted.png).
- [Nine rejected](../evidence/session-03/BF-RUN-005_v1.1_capacity-nine-rejected.png).
- [Saved state after refresh](../evidence/session-03/BF-RUN-005_v1.1_capacity-saved-after-refresh.png).

Windows desktop is known; this run's browser/version was not independently confirmed. Reset/password entry are not separately pictured. Exact observed title casing is retained above and does not affect the capacity rule.