sikuli-driver team mailing list archive

[RaiMan <question168172@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
What I definitely know:
Failure means, that a test ended with an assert exception (assert(False)).

I guess, that an error means any other exception during run of a test.
But that is exactly, what does not work: If your test scripts produce an
exception (e.g. a simple syntax error), the test IDE will simply hang,
you have to interrupt it (hopefully using the little stop button in the
transparent mini window) and in many cases you have to fully restart the
IDE to run your tests again.

Conclusion: Errors? I have never seen them ;-)

If interested: I have made a script containing a hack, that allows you to fully simulate the test run in normal IDE until it is error free. Then you can run it as real unit test without modification and get your statistics.
This example runs calc.exe on Windows.
The problem you might have is this line:
	ac = self.ac = App("Rechner")
It was scripted on a german Windows. Exchange the word "Rechner" with the title text of the window of calc.exe.

the last line
weAreInIDE(("testAdd",))
could be changed to run both tests in normal IDE:
weAreInIDE(("testAdd","testTypeNumber"))

download: https://files.me.com/rhocke/zpsan6

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