sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #40679
[Bug 1639783] Re: sikuli incorrectly matches differing images despite exact()
** Attachment added: "This is what we're looking for."
https://bugs.launchpad.net/sikuli/+bug/1639783/+attachment/4774009/+files/find_this.png
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1639783
Title:
sikuli incorrectly matches differing images despite exact()
Status in Sikuli:
New
Bug description:
We are trying to use Sikulix-1.1 for automated QA. The OS is Windows 7
professional 64bit (the java is 32-bit), we are using Jython.
In our test, we need to verify that images match exactly. To verify
the test works, we use a slightly modified image (in a way that is
significant for our test), to see if sikuli will catch the problem.
Even with find(Pattern(<image>).exact()), sikuli incorrectly assumes
the images are matched.
Interestingly, Matching Preview does NOT show the images to be matched
at precision below 0.96.
N.B. We do have Image.reset() at the start of the script, and the same
behavior occurs when launching from the command line, so this is not
an IDE image caching issue.
N.B. The background is dark but not exactly black, so this isn't the
'sikuli doesn't work correctly on black background, either', although
that's potentially a bad one for us too.
I've attached what we have on the screen, what we're looking for and
what the actual difference is (shown via red rectangle on the first
image).
Is there a way to make it work? We are now worried that all the tests
we write in sikuli are potentially useless as they don't detect
differences...
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1639783/+subscriptions
References