Scribd Logo
Upload

Welcome to Scribd!

  • 3 views

    Automation frame work

    Uploaded by

    Tarakesh

    Copyright:

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

    Automation frame work

    Uploaded by

    Tarakesh
    3 views4 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

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

    Automation frame work

    Uploaded by

    Tarakesh

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 4

    A step-by-step guide to designing a test automation framework

    1. Step 1: Define requirements. ...

    2. Step 2: Select tools and technologies. ...

    3. Step 3: Design the framework architecture. ...

    4. Step 4: Develop reusable components. ...

    5. Step 5: Implement the framework. ...

    6. Step 6: Validate and refine. ...

    7. Step 7: Document and train.

    What are different types of automation framework?

    Types of Automated Testing Frameworks

     Linear Automation Framework.

     Modular Based Testing Framework.

     Library Architecture Testing Framework.

     Data-Driven Framework.

     Keyword-Driven Framework.

     Hybrid Testing Framework.

    What are the 7 phases of STLC?

    Let us dive into the 7 phases of the software testing life cycle
    (STLC) and their importance in ensuring top-notch software
    quality:

     Phase 1 — Requirement Analysis. ...

     Phase 2 — Test Planning. ...

     Phase 3 — Test Design. ...

     Phase 4 — Test Environment. ...

     Phase 5 — Test Execution. ...

     Phase 6 — Defect Tracking. ...

     Phase 7 — Test Reporting.

    Defect States Workflow


    The number of states that a defect goes through varies from project to
    project. Below lifecycle diagram, covers all possible states

     New: When a new defect is logged and posted for the first time. It is
    assigned a status as NEW.

     Assigned: Once the bug is posted by the tester, the lead of the
    tester approves the bug and assigns the bug to the developer team

     Open: The developer starts analyzing and works on the defect fix

     Fixed: When a developer makes a necessary code change and


    verifies the change, he or she can make bug status as “Fixed.”

     Pending retest: Once the defect is fixed the developer gives a


    particular code for retesting the code to the tester. Since
    the software testing remains pending from the testers end, the
    status assigned is “pending retest.”

     Retest: Tester does the retesting of the code at this stage to check
    whether the defect is fixed by the developer or not and changes the
    status to “Re-test.”

    Implementing A Test Automation Strategy That Works For You

     Define Scope Of Automation.

     Decide On Testing Approach.

     Select A Test Automation Framework.

     Choose The Automation Tool To Use.

     Test Execution.

     Test Automation Maintenance.


     Verified: The tester re-tests the bug after it got fixed by the
    developer. If there is no bug detected in the software, then the bug
    is fixed and the status assigned is “verified.”

     Reopen: If the bug persists even after the developer has fixed the
    bug, the tester changes the status to “reopened”. Once again the
    bug goes through the life cycle.

     Closed: If the bug is no longer exists then tester assigns the status
    “Closed.”

     Duplicate: If the defect is repeated twice or the defect corresponds


    to the same concept of the bug, the status is changed to
    “duplicate.”

     Rejected: If the developer feels the defect is not a genuine defect


    then it changes the defect to “rejected.”

     Deferred: If the present bug is not of a prime priority and if it is


    expected to get fixed in the next release, then status “Deferred” is
    assigned to such bugs

     Not a bug: If it does not affect the functionality of the application


    then the status assigned to a bug is “Not a bug”.

    You might also like