sikuli-driver team mailing list archive

[Sahil Dev <question269980@xxxxxxxxxxxxxxxxxxxxx>]

New question #269980 on Sikuli:
https://answers.launchpad.net/sikuli/+question/269980

Hi,

I'm trying to understand how Sikulii works.

I have been reading the introductory documentation whoch sattes;

There are basically 3 types of tools;

1) Recorder: while you manually work along your workflow, a recorder tracks your mouse and keyboard actions. After recording, you might playback/autorun your workflow. The recordings can be edited and augmented with addition features.

2) GUI ware: The tool allows to programmatically operate on GUI elements like buttons. This is based on the knowledge of internal structures and names of the GUI elements and their features. Some of these tools have a recording feature.

3) Visually: The tools “sees” images (usually rectangular pixel areas) on the screen and allows to act on these images using mouse and keyboard simulation. There might be some recorder feature as well with this tool.

I have read the documentation on this page: http://sikulix-2014.readthedocs.org/en/latest/basicinfo.html


As stated in the introductory docuementaion Sikulii falls in the third category above.

I have many  questions and do not completely understand the working. However, I will not ask all the questions at once but try to understand my putting one question (or two) as I move on.

QUESTION: As I understand Sikulii works based on comparing the source and target images.

How are the source images generated?

Do I need to record a script of my workflow / test case and Sikulii automatically takes screenshots of my dialogs, menus, buttons and stores these as the source images?

sorry for the fundamental question but don't want to just without understanding how it works.

Thanks,



-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.