SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 3 of 3
  1. #1
    Junior Member
    Join Date
    Jan 2001
    Location
    UK
    Posts
    13
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    when not to automate? when to automate?

    Hello all -

    I am trying to establish a list of good reasons for when not to automate? and to automate?

    Here are some that i can think of:-

    When not to automate?
    1. Automation will require high maintenance
    2. Training will have to be provided for testers
    3. Not cost effective as tool will be expensive to purchase.
    ...


    When to automate?
    1. reasonably stable large application
    2. Manual testing is repetitive
    3. Regression testing purposes
    ...

    Help is appreciated.

    Viresh
    Testing consultant
    Look at my website
    http://www.vireshdoshi.com

  2. #2
    Senior Member
    Join Date
    Dec 2000
    Posts
    221
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: when not to automate? when to automate?

    There's a very good document on test automation here:
    http://www.imbus.de/engl/forschung/p...paper-1.3.html

    Especially useful is the section on 'Measurements of Expenditures' - this provides a set of formulae to determine which tests are worth automating and the 'break-even' point on each.

    Takes a bit of work to get a spreadsheet like this set up and a bit of discipline to use it when planning automation, but provides invaluable results (especially for management consumption when some pretty colours are added

    Hope this helps,

    'Automatrix'

  3. #3
    Junior Member
    Join Date
    Jul 2000
    Location
    Michigan
    Posts
    13
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: when not to automate? when to automate?

    I would recommend reading the white paper by James Hancock at: http://www.data-dimensions.com/Testers'Network/jimauto1.htm
    This paper gives you guidelines on what tests should be automated and equally important: what should NOT be automated.
    There will always be a group of tests that should not be automated. At my company we began by writing all test cases as manual, then selecting certain ones to automate, based on criteria similar to what is defined by James Hancock.

    ------------------
    Regards,

    Julia Shonka
    Warm Regards,

    Julia

 

 

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 10.71%
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 10:08 AM.

Copyright BetaSoft Inc.