Complete rename across all bundle IDs, App Groups, CloudKit containers, StoreKit product IDs, data store filenames, URL schemes, logger subsystems, Swift identifiers, user-facing strings (7 languages), file names, directory names, Xcode project, schemes, assets, and documentation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
Reflect Agent Instructions
XCUITest Workflows (Required)
When a user asks to add or update iOS UI tests, follow this order:
- Read
/Users/treyt/Desktop/code/Feels/docs/XCUITest-Authoring.md. - Use the existing test foundation (
BaseUITestCase,WaitHelpers, screen objects). - Prefer adding/updating accessibility IDs in app code first, then consume those IDs in tests.
- Run the affected suite with
-only-testingand report pass/fail. - If behavior changes broadly, run the full
Tests iOSsuite.
Hard Rules For UI Tests
- Do not use
sleep(...). - Do not use raw text selectors as the primary selector.
- Use
UITestID+ screen objects fromTests iOS/Screens/. - Keep tests deterministic via fixtures and launch flags from
BaseUITestCase. - Put new suites in
Tests iOS/and name files{Feature}Tests.swift.
Primary References
- Guide:
/Users/treyt/Desktop/code/Feels/docs/XCUITest-Authoring.md - Template:
/Users/treyt/Desktop/code/Feels/docs/templates/XCUITestSuiteTemplate.swift - Foundation helper:
/Users/treyt/Desktop/code/Feels/Tests iOS/Helpers/BaseUITestCase.swift - Wait/ID helper:
/Users/treyt/Desktop/code/Feels/Tests iOS/Helpers/WaitHelpers.swift