mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2026-11-04 08:37:30 +00:00
ui tests plan: flakes 15.4.1f and 15.4.1g from CI trial 9
This commit is contained in:
1 parent
31bda669e0
commit
53b5d2ef25
1 file changed
+8
@@ -1601,6 +1601,14 @@ Each entry gives the symptom, the cause (how it was confirmed), and the fix or m
|
||||
|
||||
- `UnreadScrollTest.unread_openChat_scrollsToFirstUnread` (GitHub emulator, trial 7, 2026-10-23): bob's CLI sent `m1`..`m60` to alice; after 60 s alice's row showed `m52` with unread 52, and nothing more arrived. In trial 5 the same wait took 574 ms. Logcat has no error in that window, and the bridge log has no per-message lines. So it is not known whether bob's CLI did not send the last eight messages or alice did not receive them. Next step: log bob's sent-message count when the wait times out.
|
||||
|
||||
### 15.4.1f Open flake: the quote kept moving before the click (desktop CI, 1 of 4 runs)
|
||||
|
||||
- `ReceivedMessagesTest.reply_received_showsQuote_clickScrollsToOriginal` (trial 9, 2026-10-23): bob's reply was composed at the bottom edge, under the message field, with the scroll-down button showing 4. Clicking its quote timed out waiting for `chat.item.quote[<id>]` to stop moving. This is the symptom of 15.4.1c on Android, seen once on desktop. Not resolved.
|
||||
|
||||
### 15.4.1g Open flake: the item info menu entry did nothing (Android CI, 1 of 3 runs)
|
||||
|
||||
- `ItemInfoTest.info_moderated_showsModeratedAt` (trial 9, 2026-10-23): after the `info` menu entry of bob's `spam` was clicked, no item info opened within 10 s. The screenshot shows the group chat with the menu closed, no alert, and no API call in flight. Passed in trials 7 and 8. Not resolved: it is not known whether the tap was lost or the app dropped the request.
|
||||
|
||||
### 15.4.2 Test strength limits (second review, 2026-10-14)
|
||||
|
||||
Under the minimal-app-code rule (item 31) some states are asserted through the model, not the UI. These tests pass if the model is right even when the UI fails to render the state:
|
||||
|
||||
Reference in new issue
Block a user