Integrating and running Web UI Test scripts in Micro Focus Application Life Cycle Management

To obtain test result details, you can integrate and run Web UI Test scripts in Micro Focus Application Lifecycle Management by using a ready-made template available in the Rational® Functional Tester installation directory.

About this task

The Web UI Test template is available in the Rational® Functional Tester installation directory. You must copy the contents of the template to a new VAPI-XP VBScript test script in Micro Focus Application Lifecycle Management, add your test script details into the VAPI-XP VBScript test script, and run the test script.

Procedure

  1. Navigate to the directory IBM\SDP\alm in the Rational® Functional Tester installation directory.

    You can use WebUI_ALM_Windows.txt file for Web UI Test scripts.

  2. Copy the contents of the template.
  3. From Micro Focus Application Lifecycle Management, create a VAPI-XP Vbscript test script.
  4. Paste the template content to the VAPI-XP Vbscript test script.
  5. Enter the test details in the VAPI-XP Vbscript test script by referring to the following table:
    ParameterDescription
    Workspace Required. Complete path to the Eclipse workspace.
    Project Required. The path, including the file name of the project relative to the workspace.
    TestsuiteName Required. The path, including the file name of the test to run relative to the project. A test can be a Web UI test, compound test, performance schedule, or an Accelerated Functional Test.
    IMSharedLocation Optional. The complete path to IBMIMShared location.
    Varfile Optional. The complete path to the XML file that contains the variable name and value pairs.
    Configfile Optional. The complete path to a file that contains the parameters for a test or schedule run.
    ResultsFile Optional. The name of the results file. The default result file is the test or schedule name with a time stamp appended.
    OverwriteResultsFile

    Optional. Determines whether a result file with the same name is overwritten. The default value is true, which means the result file can be overwritten.

    Quiet Optional. Turns off any message output from the launcher and returns to the command shell when the run or the attempt is complete.
    VMArgs Optional. You can use this parameter to pass Java virtual machine arguments.
    ProtocolInput
    Optional. You can use this parameter to run a Web UI test in parallel on different browsers. -protocolinput "all.available.targets.in.parallel=all"-protocolinput "all.available.targets.in.parallel=chrome,ff,ie" You can also specify the Web UI preferences in this argument. For example, -protocolinput "webui.highlight=<value>;webui.report.screenshots=<value>" where webui.highlight specifies whether the page element must be highlighted and webui.report specifies whether the screen shots must be captured while playing back the test in the browser. You can use this parameter to run only the failed tests from a previous playback in an Accelerated Functional Test suite.cmdline -workspace workspacename -project projectname -aftsuite aftsuitname -exportlog exportlogpath -results autoresults -protocolinput "runfailedtests=true"In the preceeding example, runfailedtests=true specifies whether the failed test from a previous playback must be rerun in Accelerated Functional Test suite.
    Note: If you use the -protocolinput argument, you must not use the following equivalent -vmargs arguments:
    -vmargs "-Dall.available.targets.in.parallel=all"
    -vmargs "-Dall.available.targets.in.parallel=browser1,browswer2,browser3"
    ExportStatsFile Optional. The complete path to a directory that you can use to store exported statistical report data.
    ExportStatReportlist Optional. A comma-separated list of absolute paths to custom report format files (.view files) that you can use to export statistical report data with ExportStatsFile.
    ExportStatsHtml Optional. The complete path to a directory that you can use to export web analytic results. The results are exported to the specified directory. You can analyze the results on a web browser without using the test workbench.
    UserComments Optional. You can add text within double quotation mark to display it in the User Comments row of the report.

  6. Run the VAPI-XP Vbscript test script.

Results

The test result details are displayed in the Output window of Micro Focus Application Lifecycle Management.