Scribd Logo
Upload

Welcome to Scribd!

  • 35 views

    AWWG Test Automation Strategy

    Uploaded by

    Nagachetan SP
    This document outlines a test automation strategy for three products - PPJ, HKT, and FCN - each with multiple language portals. It proposes using Selenium with Java, TestNG, Apache POI, and Maven to build test suites with a page object model framework and data-driven tests. Risks like test suite failures across portals are addressed. The plan outlines contributor tasks and timelines to design the framework and develop test cases over two weeks. An execution plan is defined using smoke, regression and business flow test suites.

    Copyright:

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

    AWWG Test Automation Strategy

    Uploaded by

    Nagachetan SP
    35 views3 pages
    This document outlines a test automation strategy for three products - PPJ, HKT, and FCN - each with multiple language portals. It proposes using Selenium with Java, TestNG, Apache POI, and Maven to build test suites with a page object model framework and data-driven tests. Risks like test suite failures across portals are addressed. The plan outlines contributor tasks and timelines to design the framework and develop test cases over two weeks. An execution plan is defined using smoke, regression and business flow test suites.

    Original Title

    AWWG Test Automation strategy

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines a test automation strategy for three products - PPJ, HKT, and FCN - each with multiple language portals. It proposes using Selenium with Java, TestNG, Apache POI, and Maven to build test suites with a page object model framework and data-driven tests. Risks like test suite failures across portals are addressed. The plan outlines contributor tasks and timelines to design the framework and develop test cases over two weeks. An execution plan is defined using smoke, regression and business flow test suites.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    35 views3 pages

    AWWG Test Automation Strategy

    Uploaded by

    Nagachetan SP
    This document outlines a test automation strategy for three products - PPJ, HKT, and FCN - each with multiple language portals. It proposes using Selenium with Java, TestNG, Apache POI, and Maven to build test suites with a page object model framework and data-driven tests. Risks like test suite failures across portals are addressed. The plan outlines contributor tasks and timelines to design the framework and develop test cases over two weeks. An execution plan is defined using smoke, regression and business flow test suites.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Test Automation Strategy

    V 0.1
    1. Scope
     AWWG project test automation is crucial due to frequent release cycle & each product has
    multi lingual portals.
     Test automation is feasible across the products to achieve efficient STLC.
     This document elaborates the Approach & Plan to achieve “Test Automation”

    2. Test automation approach


    Process:
     Considering 3 products PPJ , HKT & FCN with each product having multi lingual portals.
     We create individual test suits for each product
     Developing each suit on Page object model framework with Page factory using dynamic
    element identifiers would cater to multiple portals of the same product.
     As we don’t have a defined test cases in place to go with Behaviour Driven approach.
    To start with , Lets stick to Data Driven framework maintaining the test data in local excel
     Automation of existing functionalities has to be decided based on team bandwidth
     Automation of current release functionalities should be taken up in R+1 release

    Technology:
     We would only use open source tools to build this framework using Selenium with Java ,
    TestNG , Apache POI, Maven , GitHub public(TBD).
     The suit would be configured to execute on all environment & all supporting browser using
    Property files
     For now suit should be pulled to the local for each execution & any modification or new
    addition should be reviewed before pushing to Git.
     We can migrate the developed suits in future to achieve CD/CT in DevOps culture using
    Cloud based Orchestration tools

    Roles:
     Reviewer – Develop & maintain the framework & Review the new test case design
     Test case Designer – Design test case, develop test , prepare test data & execute

    3. Risk
    Description Severity Mitigation
    Time taken to develop existing Medium Manual testers to focus on
    functionality automation suit current release plan
    Automation testers to focus on
    high value business flows
    Automation suit failure on High Page layout & page elements
    different portals of same should be similar across the
    product due to single page portals of same product
    factory

    4. Plan
    TimeLine [ETA] Contributor Task Status
    11-04-22 Naga Design Framework &
    maintain
    2 Weeks Deeksha Test case development

    5. Execution Plan
     High business value E2E flow should be executed on a daily basis for all the portals
     Regression suit should be executed after each release on all the portals
     A Smoke suit would be created to be used at any instance by testers or Dev’s for Unit Testing

    6. Failure Analysis
     Environment issues - Raise a ticket with concern team
     A bug in the application under test - Flag a bug for Development
     A bug in the automation scripts - Create a task for the test team

    Thank you

    You might also like