action #35395

assert_and_click should have an option to leave the mouse

Added by zluo almost 2 years ago. Updated 10 months ago.

Status:ResolvedStart date:24/04/2018
Priority:NormalDue date:
Assignee:mkittler% Done:

0%

Category:Feature requests
Target version:Current Sprint
Difficulty:
Duration:

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.

History

#1 Updated by zluo almost 2 years ago

  • Project changed from openQA Tests to openQA Project

#2 Updated by coolo almost 2 years ago

What menu label are you talking about?

#3 Updated by coolo almost 2 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.

#4 Updated by mitiao over 1 year ago

  • Assignee set to mitiao

#5 Updated by mitiao about 1 year 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?

#6 Updated by mkittler about 1 year 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.

#8 Updated by mitiao about 1 year 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.

#9 Updated by mkittler about 1 year 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.

#10 Updated by mkittler about 1 year ago

  • Target version changed from Ready to Current Sprint

#11 Updated by mkittler about 1 year ago

  • Status changed from In Progress to Blocked

This is blocked by merging/deploying both PRs at the same time.

#12 Updated by mkittler 10 months ago

  • Status changed from Blocked to Resolved

Both PRs are finally merged now.

Also available in: Atom PDF