The rebirth of Rational Robot after XP's death
In my role as worldwide support engineer for IBM Rational Robot, I received many questions about migrating Robot to Windows 7 as Wind
Windows 7 and Rational Robot
A big difference between Windows XP and Windows 7 is security, which makes migration no picnic. The first hurdle is to set the right level of the Wind
Robot, in it's turn, uses hooks. In this context “hook” means something that picks off mouse clicks and keystrokes. Robot catches your mouse click before that mouse click does something, like clicking an OK button. Then Robot translates the mouse click into SQABasic code. That's the way recording works. For details about hooks, see Hooks Overview on microsoft.com.
You need administrator rights to use hooks, because you can't record with the default UAC settings. Record something and watch the emptiness between Sub Main and End Sub.
Windows comes in two flavors: a 32-bit version and a 64-bit version. Robot is a 32-bit application. For Robot, the 32-bit Windows is the first choice because Robot doesn't use the extra capabilities of the 64-bit version. If you start Robot in the 64-bit version, you see that Robot needs a few minutes to start. The impatient among us will hate it.
How to get Rational Robot started on Windows 7
The installation procedure is slightly different from the one that you ran on Windows XP. On Windows 7, you must disable the .NET support installation. Believe me, when you choose this option, the entire installation fails. If you need .NET support, read the following document how to get it done: "Err
I installed Robot, now what?
As I touched on before, you need to change the Windows 7 UAC setting. For full details see the following document: Prer
In the old days, Robot worked together with Rational TestManager. If you still have TestManager projects, Robot offers a tool to migrate from TestManager mode to stand-alone mode. How to use that tool, see Rati
Disable User Account Control: Run all administrators in Admin Approval Mode.
What's new in Rational Robot 184.108.40.206
The most important new features is in the field of verification points. The Rati
A verification point is a point in a script that you create to confirm the state of an
object across builds of the appl
In normal English, you can verify with a verification point whether an object is the very same in your new version as in your last version.
If you remember TestManager, you know that you could compare the result of verification point with the verification point that you recorded. Also, you could replace the verification baseline with the actual result when a verification point failed. With the arrival of the stand-alone mode, these functions became unavailable. However, in Robot version 220.127.116.11, the Comparator function is back. With this version you can also replace the baseline with the actual again.
I'd like to hear what your experiences are with the new Robot. Leave a comment or connect with me on Twit