sikuli-driver team mailing list archive

[Zeks <question267957@xxxxxxxxxxxxxxxxxxxxx>]

Question #267957 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/267957

Zeks posted a new comment:
well, I don't really know any advanced tutorial, but here is what I've
learned so far:

1) turn off automatic image naming. you'd want to work outside sikuli IDE for any serious testing and file' names should make sense cause you will not see images anywhere else
2) reuse screenshots when possible. try to place them outside top level sikuli test scripts if there is a chance that they will be needed  elsewhere
3) Modularize test scripts. Some operations are inevitably going to be shared between scripts and copy pasting them is a big no. Modularization helps code reuse as you only have ONE place to fix the code in.
4) Limit the scope the application has to search to find a match. For most windows I split them into named subregions and only perform matches within them, not a global window. If a split is made at runtime it can even compensate for small interface changes. Split is done by anchor points which really are elements that define corners of a particular region.
5) Do not debug scripts in sikuli IDE. it wastes a lot of time as it is clearly not suited for the task
6) You will most likely need to automate scripts. Learn how to use robot framework early. It really is not that hard and helps a lot
7) keep scripts in source control repository. in the end test scripts are code, same as project code and deserve same treatment
8) Sikuli currently has no error reporting on operations such as click(). Prepare to check the sanity of operations such as click(None) yourself

Keep in mind that I am a total Sikuli noob myself and I am still
learning too. Maybe someone can give better guidelines.

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