SPONSORS:






User Tag List

Results 1 to 6 of 6
  1. #1
    Junior Member
    Join Date
    Sep 2002
    Location
    Dublin, CA, U.S.A.
    Posts
    17
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    activate script remotely

    If Machine A has SilkTest installed and scripts resides there, what is the way
    to call and run the script from Machine B? Do I need to install Agent on
    Machine B? is there any other way?
    Thanks!
    bigtiger

  2. #2
    Senior Member
    Join Date
    Jul 2000
    Posts
    117
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: activate script remotely

    There are a number of answers depending on the question.

    Hate to be picky -- but could you be more specific?

    Where is your AUT? Machine A or Machine B?
    Is it just a question of invoking Silk and running the scripts (e.g. would a scheduler do) or is a question of literally CONTROLLING a Silk run from another machine?
    Would a pcAnywhere-alike do the trick for you (remote desktop control)?

    More info about your world would help generate more options, I think ...


    ------------------

  3. #3
    Senior Member
    Join Date
    Nov 1999
    Location
    Eagle, ID,USA
    Posts
    1,035
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: activate script remotely

    The agent needs to be installed on machine b. Then you would call the Connect function from Machine A to reference Machine B.

    ------------------
    Have you ever noticed? Anybody going slower than you is an idiot, and anyone going faster than you is a maniac.

  4. #4
    Junior Member
    Join Date
    Sep 2002
    Location
    Dublin, CA, U.S.A.
    Posts
    17
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: activate script remotely

    Yes, scheduler running on Machine B to do build and runtime checking. Then, a smoke test needs to be done. However, only Machine A have SilkTest installed. So, I need a way to call the Silk Scripts and kick off test on Machine A when the build on Machine B is ready. Then, on Machine A, the browser would activate and point and test the build on Machine B.

    Thanks in advance!
    bigtiger

  5. #5
    Senior Member
    Join Date
    Jul 2000
    Posts
    117
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: activate script remotely

    TonyM is correct -- you need a (licensed) copy of the Agent installed on MachineB.

    You'll then need to "coordinate" a scheduled run of SilkTest -- what we typically did was figure out when the work on MachineB would complete, add a little fudge factor, then set the schedule on MachineA to kick off SilkTest.

    Check the help for info on how to invoke SilkTest from the command-line.

    As TonyM suggests, your scripts need to first connect to MachineB, then run. This kind of "distributed" testing has some limitations -- you'll either hit 'em or you won't depending on what you're trying to accomplish. Just be aware that some functions don't work as you'd expect them to.

    Good Luck!



    ------------------

  6. #6
    Senior Member
    Join Date
    Apr 2001
    Location
    San Diego,CA,USA
    Posts
    108
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: activate script remotely

    you might want to run the smoke test on a clean machine and not the build machine hence. hence you can use this as an alternative:

    schedule the scripts to run on A wait for some file and a specific size on machine B which will tell silk that the build is done.
    Now run the installation thru silk on A
    Now determine if Installation was sucessful
    If install is sucessful tell machine to reboot itself put batch file to run silk scripts in startup which will kick off the tests as soon as machine gets restarted.

    to restart the machine without it having to ask you for a pssword on NT,XP,2K set the following registry key:

    Hkey_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon

    AutoAdminLogon=1
    DefaultUser="YOUR USER NAME"
    DefaultPassword="YOUR PASSWORD"
    DefaultDomain="YOUR DOMAIN"

    This way you don't have to mess with the build machine.

    ------------------


    [This message has been edited by AUTOMATION_GURU (edited 12-16-2002).]

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin 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 04:04 PM.

Copyright BetaSoft Inc.