eletrotupi / tcc/ commit / 468cada

frontend: drop stale pointers from the e2e flow comments

Pedro Lucas Porcellis porcellis@eletrotupi.com · 1 month ago 468cada260c6f4e13d66b237b935fb36b05ff0f1 Browse files
Parents cd4e510
Changed files
2
Additions
+5
Deletions
-5
frontend/e2e/debug-mood-components.yaml
1 1
# Debug helper (NOT part of the smoke suite): isolates the "add a mood
2 -
# component" interaction to reproduce the auto-navigation issue observed on
3 -
# 2026-09-15 (see docs/STACK.md). Run directly:
2 +
# component" interaction, i.e. the push to entry/mood-components and back
3 +
# Run directly:
4 4
#   maestro test frontend/e2e/debug-mood-components.yaml
5 5
appId: com.eletrotupi.orbit
6 6
name: Debug — mood components
7 7
---
8 8
- runFlow:
33 33
    visible:
34 34
      id: screen-mood-components
35 35
    timeout: 10000
36 36
- assertVisible:
37 37
    id: header-done
frontend/e2e/mood.yaml
1 1
appId: com.eletrotupi.orbit
2 2
name: Smoke — Mood entry
3 3
tags:
4 4
  - smoke
5 5
---
11 11
    id: button-save-mood
12 12
- extendedWaitUntil:
13 13
    visible:
14 14
      id: text-status-prefix
15 15
    timeout: 30000
16 -
# NOTE: if `screen-mood-components` times out below, the app is likely
17 -
# auto-navigating back to the entry screen right after this push — see
18 -
# docs/STACK.md "Known issues" (investigated with hierarchy dumps).
16 +
# NOTE: `screen-mood-components` is a formSheet, which on Android is a hideable
17 +
# Material bottom sheet. If it ever dismisses itself after this push, that is
18 +
# where it shows up
19 19
- scrollUntilVisible:
20 20
    element:
21 21
      id: button-add-mood-components
22 22
    direction: DOWN
23 23
- tapOn:
55 55
      id: history-list
56 56
    timeout: 15000
57 57
# Only content (data) assertion in the suite: checks the annotation we typed
58 58
# persisted on the history card. UI chrome is greeted via testIDs only
59 59
- assertVisible: "e2e smoke register"