You do not record scripts for performance testing directly as you do GUI scripts.
Instead, you record a session. After recording, Robot generates one or more scripts
from the session.
A Robot recording session contains all of the client requests and server responses
issued from the time you begin recording until the time you stop recording. Robot
stores all of the requests and responses recorded during the session in a session file
(.wch). The session file is sometimes called the "watch" file.
What You Can Record in a Session
Robot gives you considerable recording flexibility. You can record:
1. Multiple transactions. For example, you can record a data entry transaction and
a query transaction in the same recording session, one after the other.
2. Transactions against the same server or different servers. For example, you can
record one transaction against one Web server, and then record another
transaction against a different Web server.
3. Different types of requests in the same session. For example, you can record
Oracle, SQL Server, HTTP, DCOM, DBLIB, Jolt, ODBC, Socket, Sybase, and
TUXEDO requests in a session.