Scribd Logo
Upload

Welcome to Scribd!

  • 7 views

    Recommendation For QA Process: 1. Improvement Opportunity

    Uploaded by

    Emil Bose
    The document recommends implementing a test plan with specific columns to track test execution results across different platforms, operating systems, browsers, and scenarios. It also suggests holding weekly scrum meetings for the QA team led by a senior QA to share knowledge and ensure coverage of each other's work. Finally, it proposes requiring QAs to regularly update a shared features list to maintain an accurate reference and aid in onboarding new QAs. The recommendations aim to address issues like a lack of test objectives, scenario testing, interpretation of requirements, project knowledge sharing, and an outdated features list. Benefits include adequately testing scenarios, compatibility, understanding requirements, shared project knowledge, and an up-to-date reference for all QAs.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Recommendation For QA Process: 1. Improvement Opportunity

    Uploaded by

    Emil Bose
    7 views2 pages
    The document recommends implementing a test plan with specific columns to track test execution results across different platforms, operating systems, browsers, and scenarios. It also suggests holding weekly scrum meetings for the QA team led by a senior QA to share knowledge and ensure coverage of each other's work. Finally, it proposes requiring QAs to regularly update a shared features list to maintain an accurate reference and aid in onboarding new QAs. The recommendations aim to address issues like a lack of test objectives, scenario testing, interpretation of requirements, project knowledge sharing, and an outdated features list. Benefits include adequately testing scenarios, compatibility, understanding requirements, shared project knowledge, and an up-to-date reference for all QAs.

    Original Description:

    process

    Original Title

    finalasf

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document recommends implementing a test plan with specific columns to track test execution results across different platforms, operating systems, browsers, and scenarios. It also suggests holding weekly scrum meetings for the QA team led by a senior QA to share knowledge and ensure coverage of each other's work. Finally, it proposes requiring QAs to regularly update a shared features list to maintain an accurate reference and aid in onboarding new QAs. The recommendations aim to address issues like a lack of test objectives, scenario testing, interpretation of requirements, project knowledge sharing, and an outdated features list. Benefits include adequately testing scenarios, compatibility, understanding requirements, shared project knowledge, and an up-to-date reference for all QAs.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    7 views2 pages

    Recommendation For QA Process: 1. Improvement Opportunity

    Uploaded by

    Emil Bose
    The document recommends implementing a test plan with specific columns to track test execution results across different platforms, operating systems, browsers, and scenarios. It also suggests holding weekly scrum meetings for the QA team led by a senior QA to share knowledge and ensure coverage of each other's work. Finally, it proposes requiring QAs to regularly update a shared features list to maintain an accurate reference and aid in onboarding new QAs. The recommendations aim to address issues like a lack of test objectives, scenario testing, interpretation of requirements, project knowledge sharing, and an outdated features list. Benefits include adequately testing scenarios, compatibility, understanding requirements, shared project knowledge, and an up-to-date reference for all QAs.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 2

    Recommendation for QA Process

    1. IMPROVEMENT OPPORTUNITY:
    Implement Test Plan for QA team with the following columns:
    a. Item #
    b. Feature
    c. Test Execution
    d. Platform (mobile and desktop) Pass/Fail
    e. OS Version (Windows/MAC/Android/iOS) Pass/Fail
    f. Browser (Chrome/Safari/Firefox) Pass/Fail

    KEY ISSUES:
    No clear test objectives
    Lack of scenario based testing (positive/negative)
    Improper interpretation in project requirements

    EXPECTED BENEFITS:
    Both possible negative/positive scenarios will be adequately tested.
    Different kind of Browser/OS Versions/Platform will be tested (compatibility testing)
    Accurate understanding of project requirements

    NOTE:
    Include the Lead QA (if any) or at least the assigned QA in project planning/updates.
    Test planning should be performed by the QA during the last day of requirements
    gathering
    In Test planning, list the features of the project to be tested
    List also the features of the project which will not be tested. (specify the reasons these
    features wont be tested)

    2. IMPROVEMENT OPPORTUNITY:
    Implement Weekly Scrum for QA team to be handled by the Senior/Lead QA

    KEY ISSUES:
    Lack of project knowledge that handled by each QA
    Lack of team communication

    EXPECTED BENEFITS:
    Shared knowledge on how to test the feature of the project
    QA1 can handle the project of QA2 in a case of leave or emergency
    3. IMPROVEMENT OPPORTUNITY:
    Require each QA to update the Features List in google sheets every after Knowledge Sharing

    KEY ISSUES:
    Outdated features list

    EXPECTED BENEFITS:
    QA will have an updated reference of features list in all Summit sites.
    Can also help to the on boarding QAs to know our current standards

    Prepared by:

    Emil Bose
    Jr. System QA Engineer
    Summit Media

    You might also like