Scribd Logo
Upload

Welcome to Scribd!

  • 44 views

    STQA

    Uploaded by

    ankitaalai
    The document outlines a process for evaluating test automation tools which includes 3 phases: requirements gathering, tool selection, and proof of concept testing. In the requirements gathering phase, key considerations are identified such as compatibility, audience, goals, testing needs, and supported technologies. Tools are then selected that meet most of the requirements. The top tools from this evaluation undergo further analysis and proof of concept testing before a final selection is made.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    STQA

    Uploaded by

    ankitaalai
    44 views8 pages
    The document outlines a process for evaluating test automation tools which includes 3 phases: requirements gathering, tool selection, and proof of concept testing. In the requirements gathering phase, key considerations are identified such as compatibility, audience, goals, testing needs, and supported technologies. Tools are then selected that meet most of the requirements. The top tools from this evaluation undergo further analysis and proof of concept testing before a final selection is made.

    Original Description:

    Test Automation and tool evaluation

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines a process for evaluating test automation tools which includes 3 phases: requirements gathering, tool selection, and proof of concept testing. In the requirements gathering phase, key considerations are identified such as compatibility, audience, goals, testing needs, and supported technologies. Tools are then selected that meet most of the requirements. The top tools from this evaluation undergo further analysis and proof of concept testing before a final selection is made.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    44 views8 pages

    STQA

    Uploaded by

    ankitaalai
    The document outlines a process for evaluating test automation tools which includes 3 phases: requirements gathering, tool selection, and proof of concept testing. In the requirements gathering phase, key considerations are identified such as compatibility, audience, goals, testing needs, and supported technologies. Tools are then selected that meet most of the requirements. The top tools from this evaluation undergo further analysis and proof of concept testing before a final selection is made.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 8

    Test Automation &

    Tool Evaluation
    Tool Evaluation is divided into three phases:

     Requirements Gathering

     Tool Selection

     POC using selected tool


    1.Requirement Gathering

    During the requirements gathering phase of tool evaluation we have to


    list out the requirements for the automation tool. Following items will
    help for requirement list:

     Compatibility issues
     Tool audience
     Management goals
     Testing requirements
     Technology
    Compatibility Issues
    Testing tool will need to be comatible with:

    • Operating system
    • Development environments
    • ŸThird party software with which product integrates
    • ŸThe tool should also be version control friendly so that scripts created
    can be
    brought under source.
    Tool Audience

    The skills of people involved in test automation and that of the people who use
    the automation scripts is another important criterion for the test tool evaluation
    process. The benefits obtained through automation boils down to how
    effectively the tool is being put to use.
    Management Goals
    This will be based on the product roadmap and the goal for automation from
    the management perspective. Based on the product roadmap, the
    management might consider reviewing the time for which the tool has been in
    the market. They may also consider whether the tool will be upgraded
    periodically to support newer technologies. Any management will have a
    budget and will fit efforts within a given budget. So it is also important for the
    management to consider the licensing and maintenance cost of a tool and the
    additional hardware required for running the scripts.
    Technology

    When considering technology requirements in the automation perspective,


    there are two views that must be taken: Ÿ

    1. Technologies that should be supported by the tool .


    2. ŸFeatures required in the tool .
    2. Tools Selection
    While selecting tools it is important to remember that no single tool will satisfy all
    the requirements. The tool that meets most of the evaluation criteria should be
    chosen after discussion with stakeholders. Based on the tools limitations with
    respect to requirements, the automation activities must be planned. When many
    tools are found to satisfy the evaluation criteria, further analysis of tools should
    be done. Do a feature categorization by listing each tool according to the
    following features it provides:

    • Mandatory features
    • ŸDesirable features
    • ŸIrrelevant features

    Rate these features and assess as many tools as possible to prepare a short list of
    a few tools. Contact the relevant vendors and possibly ask for an evaluation
    version to run proof of concept (POC).

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy