Add F-010, F-017 UI tests and update QA test plan with 24 automation mappings

- F-010: Tap active tab scrolls to top (TabNavigationTests)
- F-017: Recent trips section with saved trips (HomeTests)
- Update SportsTime_QA_Test_Plan.xlsx with all 60 automated test mappings
- Green highlight on automated cells for visual tracking

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Trey t
2026-02-18 23:18:00 -06:00
parent d0cbf75fc4
commit dad3270be7
4 changed files with 165 additions and 34 deletions

View File

@@ -44,6 +44,39 @@ final class TabNavigationTests: BaseUITestCase {
captureScreenshot(named: "F008-TabNavigation-ReturnHome")
}
/// F-010: Tapping the active tab scrolls the view back to the top.
@MainActor
func testF010_TapActiveTabScrollsToTop() {
let home = HomeScreen(app: app)
home.waitForLoad()
// Verify "Adventure Awaits" hero card is hittable at the top
XCTAssertTrue(home.adventureAwaitsText.isHittable,
"Adventure Awaits should be hittable initially")
// Scroll down until the hero card is off-screen
for _ in 0..<8 {
app.swipeUp(velocity: .slow)
}
// Verify the hero card is no longer hittable (scrolled off-screen)
XCTAssertFalse(home.adventureAwaitsText.isHittable,
"Adventure Awaits should not be hittable after scrolling down")
captureScreenshot(named: "F010-ScrolledDown")
// Tap the Home tab (already the active tab) to trigger scroll-to-top
home.homeTab.waitUntilHittable(timeout: BaseUITestCase.shortTimeout).tap()
// Hero card should scroll back into view and become hittable
home.adventureAwaitsText.waitUntilHittable(
timeout: BaseUITestCase.defaultTimeout,
"Adventure Awaits should be hittable after tapping active tab (scroll to top)"
)
captureScreenshot(named: "F010-ScrolledToTop")
}
/// F-009: Tab state preserved Schedule filters survive tab switch.
@MainActor
func testF009_TabStatePreservedOnSwitch() {