action #46586
closed
[desktop] Missing mouse click once in a while with openQA
Added by zgao over 5 years ago.
Updated almost 3 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-documentation-x11@64bit fails in
libreoffice_mainmenu_components
Cause of failure is that mouse click is missed. And it happens at about 1 out of 15 times.
You could refer to desktopapps-documentation and desktopapps-documentation-x11 to see past failures.
It is observed that click only misses at this step, where we tried to assert and click libreoffice calc, and log tells us openQA clicked it, but it did not open.
Reproducible¶
Fails since (at least) Build 20181219 (current job)
Expected result¶
Last good: 20181218 (or more recent)
Further details¶
- Subject changed from Missing mouse click once in a while with openQA to [functional][u] Missing mouse click once in a while with openQA
- Subject changed from [functional][u] Missing mouse click once in a while with openQA to [desktop] Missing mouse click once in a while with openQA
I think this really falls in the domain of "[desktop]", the team which also maintains the more advanced desktop related testsuites, e.g. on libreoffice.
@zgao you are in "[desktop]", right? I suggest you can also use these team tags directly on creation of tickets unless you see it as a generic issue of openQA, then the ticket should be in the parent project https://progress.opensuse.org/projects/openqav3. Existing tickets can be easily moved as well. However, to me this looks like a test specific issue and not within the generic openQA behaviour.
Thank you but I might argue this is a generic openQA issue though.
We have click misses in other circumstances too
Interestingly, assert_and_click misses click at a designated test. For wayland-desktopapps-firefox, when click miss happens it happens at firefox_fullscreen.
What do you think?
This is what I mean, it only happens in specific tests :)
I would state that we do not have this issue within [functional]
- Status changed from New to Resolved
Also available in: Atom
PDF