SPONSORS:






User Tag List

Results 1 to 3 of 3
  1. #1
    Junior Member
    Join Date
    Oct 2001
    Location
    Montreal, QC, Canada
    Posts
    13
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Log Filtering in SilkTest

    Hello,
    Has anyone developed log filtering algorithms for SilkTest? When automated tests run over several days, the log files can be several megs. I was wondering what are the recommended strategies for implementing log filtering (so that we can target the part of the log that deal with problems/unexpected results). Any ideas or references to web sites/etc would be greatly appreciated. I've tried searching but keep getting stuff on filtering internet content / eventlog.

    thanks for your time,
    Steve

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

  2. #2
    Senior Member
    Join Date
    Aug 1999
    Location
    Cambridge, UK
    Posts
    470
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Log Filtering in SilkTest

    I find the best way is to normally run the scripts with the runtime options "Print agent calls" and "Print tags with agent calls" turned off. The log will then only be a few lines long for each testcase. Then if you have a fault reported, you can rerun the testcase with those options enabled, to find out what went wrong.

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

  3. #3
    Senior Member
    Join Date
    Feb 2000
    Posts
    1,497
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Log Filtering in SilkTest

    I think that you'll discover that a high percentage of the contents of a results file are caused by Print() statements. Results file size can be reduced quite dramatically by avoiding that problem before it starts. One way to do this is to write an Audit() function that replaces Print() for most uses. The characteristics of that function are that:

    1. it appends information to a global list of strings rather than print directly to the results file,

    2. it only prints to the results file when a testcase error is reported,

    3. it is list-printed and then erased in TestCaseExit().

    As testers we naturally focus our efforts on test case failures; that's where run time details are most important.

    Use Audit() calls to keep track of details that are critically important for analyzing a failure but of minimal value when the test passes.

    Reserve Print() calls for documenting critical information that you will always want to see.


    John


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

 

 

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:13 AM.

Copyright BetaSoft Inc.