Silktest and Win Runner Feature

Embed Size (px)

Text of Silktest and Win Runner Feature

  • 8/14/2019 Silktest and Win Runner Feature

    1/14

    SILK T EST AND W IN R UNNER

    F EATURE DESCRIPTIONS

    Horwath/Green/LawlerVersion 1.00 (7/6/00)

  • 8/14/2019 Silktest and Win Runner Feature

    2/14

    SilkTest and WinRunner Feature Descriptions Version 1.00 (7/6/00)

    ii Horwath/Green/Lawler

    Document Revision History This section contains a description of each revision made to this document.

    X.10 (5/21/00 tjh) initial draft.

    X.11 (6/13/00 tjh) updated with J. Greens comments and corrections.

    1.00 (6/30/00 tjh) updated with T. Lawlers comments and corrections.

  • 8/14/2019 Silktest and Win Runner Feature

    3/14

    SilkTest and WinRunner Feature Descriptions Version 1.00 (7/6/00)

    iii Horwath/Green/Lawler

    Table of Contents

    1. I NTRODUCTION 1

    1.1 Author Backgrounds.................... ................. .................. .................. ................. ................. . 12. F EATURE DESCRIPTIONS 2

    2.1 Startup Initialization and Configuration................ ............... ............... ............... ............... .. 22.2 Test Termination......................... ................. ................ ................. ................ ................... .... 32.3 Addins and Extensions ........................................................................................................ 32.4 Visual Recorders................ ................. ................. ................. ................. ................. ............. 42.5 Object Hierarchy................... ................. ................. .................. ................. ................. ......... 52.6 Object Recognition................ ................. ................. ................. ................. ................. ......... 52.7 Object Verification .............................................................................................................. 62.8 Custom Objects.......... ................. ................. .................. ................. ................. ................... . 62.9 Internationalization ( Language Localization ) ..................................................................... 72.10 Database Interfaces... ................. ................ ................. ................ ................. ................ ........ 72.11 Database Verification .......................................................................................................... 72.12 Data Driven Testing................. ................. ................. ................. ................. ................ ........ 82.13 Restoring an Applications Initial State .............. ............... ............... ............... ............... .... 82.14 Scripting Language.................. ................. ................ ................. ................. ................. ........ 92.15 Exception Handling ................. ................. ................. .................. ................. ................. ...... 92.16 Test Results Analysis......................... ................. ................. ................. ................. ............ 102.17 Managing the Testing Process.............. ................. ................ ................. ................ ........... 102.18 External Files................ ................. ................. ................. ................. ................. ................ 112.19 Debugging...................... .................. .................. ................. .................. .................. ........... 11

  • 8/14/2019 Silktest and Win Runner Feature

    4/14

    SilkTest and WinRunner Feature Descriptions Version 1.00 (7/6/00)

    Copyright 2000 1 Horwath/Green/Lawler

    1. I NTRODUCTION This document provides feature descriptions of two GUI automated test tools and theirassociated test management software:

    Mercury-Interactives WinRunner , version 6.02 (with TestDirector ) Segues SilkTest , version 5.03 (with SilkOrganizer )

    The goal of this document is to describe as objectively as possible the capabilities provided byeach tool for each feature, rather than trying to state that one tools implementation of a feature isbetter than the other. The feature descriptions made in this document are intentionally terse andcondensedtherefore subtle nuances and deep details of a feature are not covered.

    This document by itself should only be considered a good starting point for a complete test toolevaluation by those readers who are considering one of these tools for their automated testingefforts. Many excellent evaluation criteria ideas can be found in the AUTOMATED T ESTING forumon the www.betasoft.com website. Assigning a qualitative value to each feature is an evaluation

    task which depends on the test teams: testing environment, programming skills, and the application testing requirements.

    There is no substitute for using each tool to develop a specific set of prototype testcases, in orderto determine the strength and weaknesses of each tool against a typical application in yourenvironment.

    1.1 Author Backgrounds

    The following people developed this report: Terry Horwath is the primary author and a test automation consultant. He has worked with

    SilkTest, QaPartner, and SilkOrganizer since 1994. He has worked for the last year withWinRunner and TestDirector on two large web testing projects and is a TestSuite 6.0certified product specialist (CPS). Terry can be contacted at thorwath@LakeFolsom.com.

    John Green is a contributing author and owns Automation Expertise Inc., a company whichprovides customized test automation solutions. He is a recognized expert using SilkTest,QaPartner, and SilkOrganizer, working with these products since 1993. John can becontacted at jwgreen@automationexpertise.com .

    Tom Lawler is a contributing author and is a test automation consultant. He has workedwith web, VB, PowerBuilder and Terminal Emulation (TE) applications using WinRunnerand TestDirector since 1999. He is a TestSuite 6.0 certified product specialist (CPS) in bothGUI and TE and can be contacted at tom.lawler@theballardgroup.net.

    http://www.betasoft.com/mailto:thorwath@LakeFolsom.com.mailto:jwgreen@automationexpertise.commailto:tom.lawler@theballardgroup.netmailto:tom.lawler@theballardgroup.netmailto:jwgreen@automationexpertise.commailto:thorwath@LakeFolsom.com.http://www.betasoft.com/
  • 8/14/2019 Silktest and Win Runner Feature

    5/14

    SilkTest and WinRunner Feature Descriptions Version 1.00 (7/6/00)

    Copyright 2000 2 Horwath/Green/Lawler

    2. F EATURE DESCRIPTIONS For the sake of consistency alphabetical ordering was selected to describe SilkTest features first,followed by WinRunner features in each of the following sections.

    2.1 Startup Initialization and Configuration SilkTest derives its initial startup configuration settings from its partner.ini file. This

    though is not important because SilkTest can be reconfigured at any point in the session byeither changing any setting in the Options menu or loading an Option Set .

    An Option Set file ( *.opt ) permits customized configuration settings to be established foreach test project. The project specific Option Set is then be loaded [either interactively, orunder program control] prior to the execution of the projects testcases.

    The Options menu or an Option Set can also be used to load an include file ( *.inc )containing the projects GUI Declarations [discussed in section 2.6 on page 5], along with

    any number of other include files containing library functions, methods, and variables sharedby all testcases.

    WinRunner derives its initial startup configuration from a wrun.ini file of settings.During startup the user is normally polled [this can be disabled] for the type of addins theywant to use during the session [refer to section 2.3 on page 3 for more information aboutaddins ].

    The default wrun.ini file is used when starting WinRunner directly, while project specificinitializations can be established by creating desktop shortcuts which reference a projectspecific wrun.ini file. The use of customized wrun.ini files is important because onceWinRunner is started with a selected set of addins you must terminate WinRunner and restartit to use a different set of addins .

    The startup implementation supports the notion of a startup test which can be executedduring WinRunner initialization. This allows project-specific compiled modules [memoryresident libraries] and GUI Maps [discussed in section 2.6 on page 5] to be loaded. Thefunctions and variables contained in these modules can then be used by all tests that are runduring that WinRunner session.

    Both tools allow most of the configuration setup established in these files to be over-ridden withruntime code in library functions or the test scripts.

  • 8/14/2019 Silktest and Win Runner Feature

    6/14

    SilkTest and WinRunner Feature Descriptions Version 1.00 (7/6/00)

    Copyright 2000 3 Horwath/Green/Lawler

    2.2 Test Termination SilkTest tests terminate on exceptions which are not explicitly trapped in the testcase. For

    example if a window fails to appear during the setup phase of testing [i.e. the phase drivingthe application to a verification point], a test would terminate on the first object or windowtimeout exception that is thrown after the errant window fails to appear.

    WinRunner tests run to termination [in unattended Batch mode] unless an explicit action istaken to terminate the test early. Therefore tests which ignore this termination model willcontinue running for long periods of time after a fatal error is encountered. For example if awindow fails to appear during the setup phase of testing, sub