SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 4 of 4
  1. #1
    SQA Knight
    Join Date
    Jul 1999
    Location
    Grand Rapids, MI
    Posts
    3,727
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    GUI object names in the script

    While I wait for an evaluation copy of
    Robot I am carefully reviewing the
    documentation provided by Rational.

    I am confused with the aspect of how
    a GUI object, window, etc. is referenced in a
    script--specifically it appears that Robot
    does not use a "GUI Map" (as in
    WinRunner), or a "GUI declaration file"
    (as in Silk) to identify an object.

    Am I correct in assuming that Robot
    forgoes the step of mapping a
    programmer defined "identifier" (later used
    in a script) with one or more OS dependent
    "characteristics" (a "physical description"
    in WinRunner and a "tag" in Silk)?

    It appears from the Robot user guide that
    you use the OS dependent "characteristic"
    (which appears to be an internal object name,
    text caption, Index #, or ID #) directly in the script to reference the object? Is
    this correct?

    - Thanks, Terry Horwath

  2. #2
    Junior Member
    Join Date
    Jan 2000
    Location
    Manchester
    Posts
    2
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: GUI object names in the script

    Yes, that is true.

    Windows are referenced via captions. eg
    [Window SetContext, "Type=Window;Caption=Export",""]

    Controls are referenced by a variety of means, including ObjectID, Text or ObjectIndex. For example
    [PushButton Click, "Text=OK"]
    or
    [ComboBox Click, "Label=Country:", ""]

    This can get dangerous with regard to window captions changing, so we found that the best way to tackle it was to functionalise the Window Context Setting. ie Create a library of sub procedures specifically for setting the context of windows. Then you only need a function call to set the context. Also, if a window caption changes, only one line needs to be updated, not hundreds of scripts.

    Likewise, referencing controls by ID is not ideal and so Text referencing is both more reliable and makes the code much more readable.


    [This message has been edited by Archie Moore (edited 01-04-2000).]

    [This message has been edited by Archie Moore (edited 01-04-2000).]

  3. #3
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: GUI object names in the script

    User andy wong (AWong@exceedcommerce.com.nospam) posted:

    Hi All,

    Does anybody know what the ATL means in this statement:

    GenericObject ScrollLineDown, "Class=ATL:0584AB80;ClassIndex=1", ""

    and does anybody know why the id number following the ATL changes
    sometimes.

    Thanks in advance.

    Andrew Wong
    Exceed Internet Commerce

    ---

  4. #4
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: GUI object names in the script

    User Graeme Flack (graeme.flack@crystaldecisions.com.nospam) posted:

    Hi

    We had a similar problem with our composite ActiveX controls.

    The number is assigned by the system the first time it creates a window of
    this type. This number is then always used for this type of window, until
    the machine is switched off. Next time the machine is used, the number will
    be assigned again.

    There is a C++ macro which can be used in the declaration of your class
    called DECLARE_WND_CLASS macro (see MSDN), which allows you to set a user
    defined class name which won't change. This should solve the problem of the
    number changing and make the scripts more manageable.

    Regards,

    Graeme Flack | QA Analyst | Crystal Decisions http://www.CrystalDecisions.com
    Access. Analyze. Report. Share



 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 12.50%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 08:31 AM.

Copyright BetaSoft Inc.