background image
<< How to Split a Session into Multiple Scripts | Display returned data value >>
<< How to Split a Session into Multiple Scripts | Display returned data value >>
Importing a Session
Recording Sessions
Alternatively, to cancel the requests you made since you began recording the
current script, click Ignore just-recorded information. This action affects only
the current script, not any previous scripts you recorded in this session. For
more information, see Cancelling Scripts During Recording on page 7-10.
3. Click OK.
4. Repeat the previous steps as many times as needed to end one script and begin
5. After you click the Stop Recording button to end the recording session, type or
select a name for the last script you recorded, or accept the default name.
Importing a Session
You can import a session from a different computer into your current project. For
example, assume someone at another site e-mails you a session file. You can import
this session file, regenerate scripts, and create a suite.
Upon importing a session into Robot, you are asked whether you want to generate
the scipts contained within the imported session. To do so, click Yes, and the scripts
are generated and opened in the appropriate editor.
To import a session file and regenerate scripts:
1. In Robot, click Tools > Import Session. The Open dialog box appears.
2. Click the session file, then click Open. The session and its scripts are now in
your project.
3. To regenerate the scripts in the session you imported, click Tools >
Test Scripts from Session, and select the session you imported.
4. To regenerate the suite, click Tools >
Rational Suite TestStudio > Rational
5. Click File >

New Suite. The New Suite dialog box appears.
6. Select Existing Session, and click OK.
7. TestManager displays a list of sessions that are in the project. Click the name of
the session that you imported, and click OK.
TestManager automatically creates a suite that is ready to run.
Regenerating Scripts from a Session
You might want to regenerate a session's scripts for a variety of reasons--for
example, to overwrite edits you made to the original scripts (restoring the scripts to
the original recorded transactions), or to change the script generation options.