action #35395
closedassert_and_click should have an option to leave the mouse
0%
Description
we have atm mouse_set using coordinators, it will be helpful directly to use mouse_set by using menu label (id).
For multiple menu levels this is a good option.
Updated by zluo over 6 years ago
- Project changed from openQA Tests (public) to openQA Project (public)
Updated by coolo over 6 years ago
- Subject changed from openQA API feature mouse_set - should be able to set menu label ( id ) to assert_and_click should have an option to leave the mouse
- Category set to 136
- Target version set to Ready
Discussed with zlou in person - he mixed a mouse clicking problem in yast widgets with https://hackweek.suse.com/16/projects/make-yast-testing-independent-of-keyboard-shortcuts
From what I understand the real problem is that assert_and_click moves the mouse to a hidden place which in zlou's use case hides the menu he wants to click in a 2nd step.
Updated by mitiao about 6 years ago
so only give an option to leave mouse? i don't get fully understand, could you provide an instance to show the case or any other suggestion?
Updated by mkittler about 6 years ago
@mitiao Are you still working on this?
As I understand the issue, it would be about conditionally skipping
if ($old_mouse_coords->{x} > -1 && $old_mouse_coords->{y} > -1) {
return mouse_set($old_mouse_coords->{x}, $old_mouse_coords->{y});
}
else {
return mouse_hide();
}
in testapi::assert_and_click. So that would be another optional parameter to keep the mouse where the click was done.
Updated by mitiao about 6 years ago
- Status changed from New to In Progress
Updated by mitiao almost 6 years ago
- Assignee changed from mitiao to mkittler
the PRs has been approved and waited for merge.
@mkittler i am re-assigning this ticket to you since i am leaving today
could you help to take over the PRs and push them to repo? thanks.
Updated by mkittler almost 6 years ago
Ok. So what's currently blocking this is that we have to sync os-autoinst and test code deployment. I'll also resolve the conflicts on the test code PR.
Updated by mkittler almost 6 years ago
- Target version changed from Ready to Current Sprint
Updated by mkittler almost 6 years ago
- Status changed from In Progress to Blocked
This is blocked by merging/deploying both PRs at the same time.
Updated by mkittler over 5 years ago
- Status changed from Blocked to Resolved
Both PRs are finally merged now.