Is RobotJ worth the headaches?
I'm in QA, and our testing scripts are currently in Robot. I've been evaluating/playing around with RobotJ, trying to learn a little Java in the process.
The only benefit I can see with this is that someone who Already knows Java (a developer) could ramp up to speed a lot faster on RobotJ than with Robot, and the RobotJ scripts could be more easily maintained if you know Java.
But even this benefit seems a little useless, because in my experience most developers can catch on to regular Robot SQA very fast anyway.
If you're reading this, pls let me know what your experiences are, maybe I'm missing something here.
Re: Is RobotJ worth the headaches?
I agree with your point. If you application is all web/html based and if you have scripts all done in SQARobot and working smooth then its no point switching over. But I've found SQARobot on html application is lot harder to automate as Robot does not recognise many of the objects on the screen and the automater has to code more and have work arounds. Whereas RobotJ recognises those objects straight away but ofcourse the Java learning is quite steep, but exciting...