sikuli-driver team mailing list archive

[sdraganov <question670579@xxxxxxxxxxxxxxxxxxxxx>]

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

I'm facing probably very common issue but don't know what the best way to deal with it.
The issue is that I'm running one sikuli-script that runs the same test over and over again, and if something goes wrong it just stops.
Currently it takes about 3-4 hours to complete the entire test and that time constantly increases because of adding more functionality. Very often the script stops because of missing image, and I am wondering is there a way to tell sikuli to not stop entire test but to do some operations like quit running program and continue running script from specific place.

 The obvious way to resolve this is probably by separating that giant test to number of small one, but here is the catch. The script is not that big at all, it just repeats around 80 times. I don't know how to split it to 80 individual tests since those repetitions depends from the number of the builds that are about to be tested. I place the builds into a folder, read it's content, then I loop the script for each of the builds into the folder. The number of the builds is not the same each day so I can't hardcode 80 individual tests.

May someone share a reliable way to deal with this case? What I want basically is if something fails to stop immediately, close everything started by the script, and restart it from begging. 

I am open for any ideas. Maybe the entire logic of my tests is senseless but I really have no idea how to do it.

Here is a video from my latest test which failed because of missing image at ~38min.
https://drive.google.com/file/d/1PuIQ3ZwWbSr2qpyUlLRUwVKbrpB5np2i/view?usp=sharing


-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.