MarketSquare / MarketSquare/robotframework-SikuliLibrary
Click In is Broken in certain cases. Request Click At Offset
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 163
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
For whatever reason, the "Click In" keyword seems to have this behavior:
First it finds image1 on the screen.
Then it finds image2 on the screen.
Then it clicks on the found image2.
Then it looks for image2 on the screen.
It works fine if nothing changes immediately after the click, but say you're clicking a radio button, or a + button that becomes a - once it expands a menu, or you are closing a window. In any of these situations the command does it's job and clicks where it needs to, and then reports failure, it could not find the image to click on.
The system I am running it on is Centos 6, and I cannot confirm if it works or does not work this way on other systems. I do not have them at my disposal.
This issue can be alleviated by creating a "Click At Offset" keyword that takes the image parameter, an X offset parameter, and a Y offset parameter that is number of pixels from the upper left hand corner of the image. This functionality already exists in Sikulix, and would simply be adding parameters to the filename for the image string that is given to Sikulix.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the existing "Click In" keyword and its SikuliX call, then reproduce the radio-button, expanding-button, or window-closing cases described. Done should include a "Click At Offset" keyword accepting an image and X/Y offsets, without reporting failure after the click changes or removes the image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100