sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #16915
Re: [Question #223428]: Major Diff and Comparision of sikuli with selenium and Qtp
Question #223428 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/223428
Status: Open => Answered
RaiMan proposed the following answer:
-- since Skuli is "only" some Java API, that supports visual searching
(and some other features supported by Java Robot), it cannot be compared
with a high level testing system like QTP. It is something like a low
level plugin, to support visual testing and automation.
-- vs. Selenium: Selenium has some knowledge of the internal structure
of the web app. Sikuli is just WYSIWYS; What You See is What You Script.
Sikuli only deals with visual stuff an app produces on the real screen
and has no knowledge about any app internals.
-- So talking about testing. the "only" thing you can do is
assert exists("some_image.png")
which means: try to find the given image on the screen in this moment - not found = fail, found = pass
where some_image.png is a given (partly) rectangle screenshot (just w * h pixels).
-- talking about text (findText/getText in/from some region on the screen)
Sikuli internally uses Tesseract (currently 2.04) and has some possibilities to find a given text or read (OCR) the text in a region. the accuracy is rather poor in the moment, so it might not be sufficient for professional testing.
But you have to try, since it depends on the used font and foreground/background color.
About other aspects like running on different systems and remote support
search this question forum and look at the faqs here.
asking google using "sikuli" "other keyword" might reveal some more
information.
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.