Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to have multiple versions of an reference image #15

Open
Tattoo opened this issue Mar 6, 2016 · 6 comments
Open

Ability to have multiple versions of an reference image #15

Tattoo opened this issue Mar 6, 2016 · 6 comments

Comments

@Tattoo
Copy link
Contributor

Tattoo commented Mar 6, 2016

It would be handy if IHL could automatically check screenshot against multiple versions of same reference image. One idea could be to have the reference image name to be either a .png file or a folder -- in latter case, all images from under that folder could be tried.

For example, given:

reference_images/
    ├── button_cancel.png
    ├── button_save.png
    ├── popup_notification/
    │   ├── linux.png
    │   ├── osx.png
    │   └── windows.png
    └── window_title_main.png

If one would do:

Wait for    popup notification

then IHL would try each picture from that folder.

Main motivation is that right now, you would need to do this handling inside Robot Framework or force you to make a library yourself.

@stade
Copy link

stade commented Mar 7, 2016

👍

@Tattoo
Copy link
Contributor Author

Tattoo commented Apr 14, 2016

Do notice, that the spec is meant to be working on all recognize-related keyword.

In other words, given the example above, also these should work:

Wait for    popup notification
Locate    popup notification
Click Image    popup notification

and so on

@suonto
Copy link
Contributor

suonto commented Apr 15, 2016

Fixed in 604f720

@suonto suonto closed this as completed Apr 15, 2016
@Tattoo
Copy link
Contributor Author

Tattoo commented Apr 13, 2017

Not yet documented

@aaltat
Copy link

aaltat commented Apr 13, 2017

What documentation still missing?

matejc added a commit that referenced this issue Apr 17, 2020
@damies13
Copy link

From reading the documentation is seems this has been implemented and documented already? is something missing? or should this issue be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants