eletrotupi / tcc/ frontend/e2e/mood.yamlcd4e510347589b652e51c97c5db46b27392f76da
1.4 KB | 59 lines Raw
1
appId: com.eletrotupi.orbit
2
name: Smoke — Mood entry
3
tags:
4
  - smoke
5
---
6
- runFlow:
7
    file: helpers/_login.yaml
8
- tapOn:
9
    id: mood-great
10
- tapOn:
11
    id: button-save-mood
12
- extendedWaitUntil:
13
    visible:
14
      id: text-status-prefix
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).
19
- scrollUntilVisible:
20
    element:
21
      id: button-add-mood-components
22
    direction: DOWN
23
- tapOn:
24
    id: button-add-mood-components
25
- extendedWaitUntil:
26
    visible:
27
      id: screen-mood-components
28
    timeout: 15000
29
# The sheet opens at its half detent and the component list scrolls, so only the
30
# first rows are mounted
31
- tapOn:
32
    id: component-joy
33
- tapOn:
34
    id: header-done
35
- tapOn:
36
    id: input-notes
37
- inputText: "e2e smoke register"
38
- hideKeyboard
39
- tapOn:
40
    id: button-save-entry
41
- extendedWaitUntil:
42
    visible:
43
      id: text-mood-saved
44
    timeout: 30000
45
- tapOn:
46
    id: button-conclude
47
- extendedWaitUntil:
48
    visible:
49
      id: text-welcome-quick-register
50
    timeout: 15000
51
- tapOn:
52
    id: tab-history
53
- extendedWaitUntil:
54
    visible:
55
      id: history-list
56
    timeout: 15000
57
# Only content (data) assertion in the suite: checks the annotation we typed
58
# persisted on the history card. UI chrome is greeted via testIDs only
59
- assertVisible: "e2e smoke register"