Hello, Thanks for the answer. However, I think this solution is not suitable for our purposes. Actually, we are running tests via a UTScapy campaign file, in which we call plenty of Sikuli scripts to retrieve the exit status (OK/KO) of each Sikuli script (which corresponds to a specific part of our GUI or a specific scenario). That's why we need to break down the GUI testing part into a multitude of Sikuli scripts, which have to be called separetely.
-- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1256808 Title: [request] Pre-loading Sikuli's Environment Status in Sikuli: New Bug description: Hello, Currently we're running testing campaigns with a certain number of Sikuli scripts. Sometimes, we run one or several scripts a given number of times (could be more than 1000 times), and we retrieve the returned error code. The main problem is that each time we run a Sikuli script, Sikuli loads its environment first (yellow frame), which in our case increases significantly the overall execution time (each environment loading takes like 3.4 seconds that you multiply by the number of Sikuli scripts executed ..). Wouldn't be possible to pre-load Sikuli's environment (kind of daemon mode) ? This way I will only have to load Sikuli's environment once and save a lot of time. I apologize in advance if this feature already exists but I haven't seen any mention of it in docs or on the website. NB : we're using Sikuli IDE 1.0.1 x64. Regards, secwineman To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1256808/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
