sikuli-driver team mailing list archive

[RaiMan <question189436@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
at 1:
Think this is answered in the other question by ma last comment

at 2:
This is some kind of global variable. If you would work with classes, this would be rather easy.
With your current approach you can use Sikuli's class Settings 
(look https://answers.launchpad.net/sikuli/+question/189351 Commenrt #2)

# 3:
If you ant to do serious testing, using Pythons unit test is a must (see FAQ ).
The HTMLTestRunner is really nice and easy to adopt to your needs (I have a version, that automatically makes screen shots on failure, that can be clicked to open in the HTML report)

# 4:
This is currently not possible with the means of pure Sikuli. If you have changed something in your workflow, you have to start from scratch. Normally what hurts, is that normally the setUp() and tearDown() actions have to be run again, if a test is reworked.
This can be made a little bit easier, by adding some coding, that realizes, what is already done.

A real debugging feature is only available, when you switch to Eclipse
or Netbeans using there Python plugins.

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