com.rational.test.ft
Class rational_ft

java.lang.Object   com.rational.test.ft.rational_ft

public class rational_ft
extends java.lang.Object

Command-line interface for Functional Test. From the command line you can perform the following tasks:

• Record a script
• Compile a script
• Play back a script, passing command-line arguments to the script
• View and edit verification-point and object-map files
• Invoke the Java/HTML enabler
• Invoke the Application Configuration Tool
• Run Functional Test unattended in batch mode
• Write an application config for a .NET application

Command Line Usage:

The beginning of the rational_ft command line can come in one of two primary forms. In the text below we refer to either of these beginnings as <rational_ft>.

• java -classpath rational_ft.jar com.rational.test.ft.rational_ft
• java -jar rational_ft.jar

Note that you should use the first version of the command line if you use PurifyPlus.

• Record a new script:
  <rational_ft> -datastore <directory> [-map <sharedmap>] [options] -record <script-name>
• Record into an existing script, inserting before or after a given line:
  <rational_ft> -datastore <directory> [-insertbefore <line>] [-insertafter <line>] [-map <sharedmap>] [options] -record <script-name>
• Compile a script:
  <rational_ft> -datastore <directory> [options] -compile <script-name>
• Play back a script, passing command-line arguments <values> to the script:
  <rational_ft> -datastore <directory> -log <logname> [options] -playback <script-name> [-args <values>]
• Play back a script, with an associated datapool:
  <rational_ft> -datastore <directory> -iterationCount <count|ALL> [options] -playback <script-name>
• Play back a script that uses classes from other Functional Test projects
  <rational_ft> -datastore <directory> -projectpath <reference-project-path> -playback <script-name>
• Record, compile, and play back a script:
  <rational_ft> -datastore <directory> [options] -record <scriptname> -compile -playback [-args <values>]
• Construct an empty script:
  <rational_ft> -datastore <directory> -map <sharedmapname> [options] -create <scriptname>
• Regenerate the helper file for a script:
  <rational_ft> -datastore <directory> [options] -helper <scriptname>
• Regenerate all helper files for a datastore:
  <rational_ft> -datastore <directory> [options] -regenHelpers
• Display a verification-point file or object-map file:
  <rational_ft> -datastore <directory> [options] -display <file>
• Edit a verification-point file or object-map file:
  <rational_ft> -datastore <directory> [options] -edit <file>
• Create and edit a shared-object map:
  <rational_ft> -datastore <directory> -fromMap <existingmap> [options] -createMap <mapfile>
• Merge a later version of an object map into a current (modified) version of the same map. (Used for CMVC version updating):
  <rational_ft> -datastore <directory> [options] -from <sourcemapname> -to <targetmapname> [-original <commonmapname>] -mergeMap
• Compare an actual verification point result to an expected verification point result:
  <rational_ft> -datastore <directory> [options] -baseline <vpname> -compare <expectedfile> <actualfile>
• Run the Java/HTML/Eclipse enabler:
  <rational_ft> -enable [enabler-arg]
  where enabler-arg can be:
  • ALL searches all drives and enable all found browsers, Java environments, and Eclipse platforms
  • <dir> enables the browser, Java environment, or Eclipse platform in the given directory
  • (empty) runs the enabler interactively
• Enable a configured browser, Java environment, or Eclipse platform:
  <rational_ft> -enableName [configured-name]
  where configured-name is the logical name of the browser or Java environment configured by the Enabler that will be enabled
• Disable all configured browsers, Java environments, and Eclipse platforms:
  <rational_ft> -disableall
• Run the Application Configuration Tool:
  <rational_ft> -appConfig [config-arg]
  where config-arg can be the logical name of an app to center on
• Run the Test Object Inspector:
  <rational_ft> -inspector
• Write a config for a .NET application:
  <rational_ft> -writeconfig [executable-including-path]
  where executable-including-path is the fully qualified path to the executable

For commands that take a <script-name>, the name can be a simple identifier, or it can use Java package syntax. For example:

• To record a script test1.java using . as the datastore directory:
  <rational_ft> -datastore . -record test1
• To record a script test2.java that lives in a package subdirectory:
  <rational_ft> -datastore . -record subdir.test2

For the commands where options can be specified, available options are:

• -<option-name> <value> set the option to the value
• -reset <option-name> reset the option to its default value
• -resetall reset all options to their respective default values
• -args <values> command-line arguments to be passed to the playback script
• -datapool <datastore-relative-name> sets the shared datapool name
• -helpersuper <helper-class-name> the helper superclass name to be used when generating the helper file
• -iterationCount <intteger|ALL> the number of times the script will be iterate over the associated datapool.

For example, -rt.log_format none specifies that no log gets displayed. Supported options and their values are listed in IOptionName. To run Functional Test unattended in batch mode with a TestManager log, you need to include the following options on the rational_ft command line:

• -user <username> the TestManager user name for login
• -password <password> the TestManager password for login. (Optional)
• -project <fullpath and full projectname> the name of the TestManager project, which is preceeded by its pull path. This is case sensitive.
• -build <build> the name of an existing TestManager build.
• -logfolder <foldername> the name of an existing TestManager log folder.
• -log <logname> the name of the TestManager log.

Example:

java -classpath C:\IBM\RFT\FunctionalTester\bin\rational_ft.jar com.rational.test.ft.rational_ft -datastore e:\myProject -playback script.Test -user swalton -password swordfish -project e:\RationalProjects\myProject.rsp -build "build 1" -logfolder default -log myLog

or

java -jar C:\IBM\RFT\FunctionalTester\bin\rational_ft.jar -datastore e:\myProject -playback script.Test -user swalton -password swordfish -project e:\RationalProjects\myProject.rsp -build "build 1" -logfolder default -log myLog

Since:

RFT1.0

Nested Class Summary

protected static class

rational_ft.Debug

Constructor Summary

rational_ft()

Method Summary

protected static void	debug(java.lang.String message)
protected static void	debug(java.lang.String message, int severity)
static void	main(java.lang.String[] args) Entry point for the Java application.
protected static void	main(java.lang.String[] args, java.lang.String eclipseApplicationName) This method allows for multiple entry points to RFT with different command processing needs but similar class loading setup.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

rational_ft

public rational_ft()

Method Detail

main

public static void main(java.lang.String[] args)

Entry point for the Java application. The command line now runs as an eclipse application. So we need to: 1) Find the eclipse directory and the startup jar inside it. 2) Put the startup.jar into a classloader and load the startup passing it a

Since:

RFT1.0

main

protected static void main(java.lang.String[] args,                            java.lang.String eclipseApplicationName)

This method allows for multiple entry points to RFT with different command processing needs but similar class loading setup. For instance the rational_ft main can use this methods as well as the Hyades test suite run support. The general idea is that the classpath for RFT is generally incomplete and this code resolves those issues and allows users to focus on the classes that scripts use and not the JARs/DLLs needed by RFT.

debug

protected static void debug(java.lang.String message)

debug

protected static void debug(java.lang.String message,                             int severity)