Re: [Sikuli-driver] [Question #261759]: Running Sikulix Tests on a VM via Jenkins: click() is reported, but not done really
Question #261759 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/261759 Rocky posted a new comment: Thats a big limitation of Sikuli . I have hit the ditto same problem and i have left no stone unturned to solve this issue , it seems i will also have to go for brute force approach. i.e. keep one machine just for sikuli , thats quite an investment . -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #261759]: Running Sikulix Tests on a VM via Jenkins: click() is reported, but not done really
Question #261759 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/261759 Alessandro Capello posted a new comment: The solution is kind of brute force. We got an old laptop on which we run the tests. The laptop itself isn´t locked so that sikulix can run the tests. I don´t like this solution but it´s the only thing I could have thinked of doing right now. If there is anything better which doesn´t require a huge investment/effort, I would be delighted to hear that ;) regards Alessandro -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #261759]: Running Sikulix Tests on a VM via Jenkins: click() is reported, but not done really
Question #261759 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/261759 RaiMan posted a new comment: So what did you find as a solution? -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #261759]: Running Sikulix Tests on a VM via Jenkins: click() is reported, but not done really
Question #261759 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/261759 Summary changed to: Running Sikulix Tests on a VM via Jenkins: click() is reported, but not done really -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #261759]: Running Sikulix Tests on a VM via Jenkins: click() is reported, but not done really
Question #261759 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/261759 RaiMan posted a new comment: What if you just leave the RDP session open, but minimize the RDP window? --- about the background: The machine, where a Sikuli workflow is running, must have a Java GraphicsEnvironment with at least one useable GraphicsDevice. In situations without a real screen (like on headless systems, in VM's or with any remote RDP/VNC sessions) it might run or not, depending on how the GraphicsDevice situation is seen by Java at startup of a Sikuli script. Results are not predictable, if the underlying GraphicsDevice situation changes somehow, while a script is working. Since you say, that the clicks are reported correctly, but are not really executed, then at least there must be a GraphicsDevice in all situations, since the find(button) works (internally using Java Robot's createScreenCapture). Mouse actions are triggered by utilizing Java Robot's appropriate features. The downside of this is: Sikuli does not know anything about wether the click for example is really done and reached the targeted application, because Java Robot does not know either. That a click is reported but not done in reality is in most cases only reported for usages on Windows systems. In most cases it has something to do with UAC and can be overcome with running as admin. But I guess this is not the solution in your case. So for now: it either works or not - no special fixes, only experiences, about environments where it works and where not. -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #261759]: Running Sikulix Tests on a VM via Jenkins
Question #261759 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/261759 Status: Open => Solved Alessandro Capello confirmed that the question is solved: ... I'm truly sorry for asking this question. Sadly I haven't got any search results for my question so I started writing it. It must have been a bug or just the search engine who failed. Could someone please close the question because I read the answer on the board. regards Alessandro -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #261759]: Running Sikulix Tests on a VM via Jenkins
New question #261759 on Sikuli: https://answers.launchpad.net/sikuli/+question/261759 Hi everyone, I have an issue with the Sikulix 1.1.0 version. My Scenario: > I have an jenkins instance which continuously triggers a maven build which is ran on a virtual machine. The job contains just a simple setup followed by an execution of a very simple sikuli test (Open firefox -> paste url -> press buttons, nothing fancy) < The problem which I'm currently facing is that the test won't get executed on the vm. The weird thing is that sikulix still logs the actions but without executing them. My first thought was that the vm had any problems (like missing write privileges) but after executing the test manually with success all those concerns were gone. I always log on to the vm via RDP (Win-> Win). My guess is that when leaving the vm (still be logged on but not watching the vm desktop) the test won't get executed. Is this a common problem? And are there maybe some fixes? regards Alessandro -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
