SAP / ui5-webcomponents

UI5 Web Components - the enterprise-flavored sugar on top of native APIs! Build SAP Fiori user interfaces with the technology of your choice.
https://sap.github.io/ui5-webcomponents/
Apache License 2.0
1.52k stars 263 forks source link

[ui5-list]: regularly failing tests #9173

Closed nnaydenow closed 3 months ago

nnaydenow commented 3 months ago

Bug Description

[chrome-headless-shell 125.0.6422.141 linux #0-2] Running: chrome-headless-shell (v125.0.6422.141) on linux
[chrome-headless-shell 125.0.6422.141 linux #0-2] Session ID: 89c375a1efad80b5a4f8ede8d6abcab0
[chrome-headless-shell 125.0.6422.141 linux #0-2]
[chrome-headless-shell 125.0.6422.141 linux #0-2] » /test/specs/List.spec.js
[chrome-headless-shell 125.0.6422.141 linux #0-2] List Tests
[chrome-headless-shell 125.0.6422.141 linux #0-2]    ✖ tests 'loadMore' event fired upon infinite scroll
[chrome-headless-shell 125.0.6422.141 linux #0-2]
[chrome-headless-shell 125.0.6422.141 linux #0-2] 51 passing (48.6s)
[chrome-headless-shell 125.0.6422.141 linux #0-2] 1 failing
[chrome-headless-shell 125.0.6422.141 linux #0-2]
[chrome-headless-shell 125.0.6422.141 linux #0-2] 1) List Tests tests 'loadMore' event fired upon infinite scroll
[chrome-headless-shell 125.0.6422.141 linux #0-2] The event loadMore must be fired
[chrome-headless-shell 125.0.6422.141 linux #0-2] Error: The event loadMore must be fired
[chrome-headless-shell 125.0.6422.141 linux #0-2]     at async Context.<anonymous> (file:///home/runner/work/ui5-webcomponents/ui5-webcomponents/packages/main/test/specs/List.spec.js:400:3)

Affected Component

ui5-list

Expected Behaviour

No response

Isolated Example

No response

Steps to Reproduce

1. 2. 3. ...

Log Output, Stack Trace or Screenshots

No response

Priority

High

UI5 Web Components Version

nightly

Browser

Chrome

Operating System

No response

Additional Context

No response

Organization

No response

Declaration

kgogov commented 3 months ago

Hello @nnaydenow,

I looked into the issue but was unable to produce it locally. However, I've uploaded a change (#9191) that I think should help resolve the issue.

Here are my parameters on my machine:

Screenshot 2024-06-12 at 11 03 42 Screenshot 2024-06-12 at 11 20 29