1 / 18

Project Name - Testing Iteration 1 UAT Kick-off

Project Name - Testing Iteration 1 UAT Kick-off. Contents. Iteration 1 Overview. Iteration 1 consists of 43 user stories Out of 43, 17 are functional & 23 are data user stories Campaign type “Auto Pay” would be run as part of the campaign execution process.

cfoster
Download Presentation

Project Name - Testing Iteration 1 UAT Kick-off

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Project Name - TestingIteration 1 UAT Kick-off

  2. Contents

  3. Iteration 1 Overview • Iteration 1 consists of 43 user stories • Out of 43, 17 are functional & 23 are data user stories • Campaign type “Auto Pay” would be run as part of the campaign execution process

  4. CCM Test Metrics / Communications Weekly View • For the foundational release, there are two proposed types of testing communications: • Defect Management Meetings (Dailyat TBD) • Internal Deloitte team meeting • Defect Management Reports (Dailyat TBD ) • Published externally to our clients

  5. Defect Management Meetings • Purpose • Review new defects • Identify appropriate developer for triage • Receive status update on defects in development and defects that failed re-test • Identify next steps to achieve a fix • Determine estimated fix date based on priority / severity • Identify items that are being handed back and forth, requiring escalation to testing leadership • Determine if escalation is needed for high severity or high aging defects, and subsequently work with Test Governance Lead to address • Meeting Format • Facilitator to walk through open defect export from CCM Test project in Quality Center • Defect ID • Severity • Developer Assigned • Status • Summary • Comments • Developers to make real-time updates to defects in Quality Center Required Fields When Opening a Defect • Proposed Facilitator • Defect Managers • Proposed Attendees • Developers • Defect Manager • Test Managers • Test Data Manager • Test Governance Lead (optional) • Proposed Timing • Daily • 1 hour

  6. Test Execution Process

  7. Roles and Responsibilities

  8. Indicates step as passed Yes Closes defect Yes Test Test Executes Tester Logs a defect with Executes Case No Case test case supporting details retest Passes ? Assigns defect Passes ? No back to developer group Receives defect assignment Defect Manager Developer Defect Management Process • The defect management process is as follows: Defect Management Process Assigns back to tester Assigns it to Appropriate person Developer fixes the code and assigns it back to defect manager

  9. Iteration 1 UAT Logistics • All test cases should be executed directly into Quality Center • Test cases should not be executed in offline tools and later “mass updated” in Quality Center, as all metrics / reporting will be based real-time out of Quality Center • If you have issues accessing Quality Center, please reach out to Name/Emailto determine an alternate testing approach • Defects should be created directly from failed test steps within test cases and linked accordingly • This will show the correlation between failed test cases and defects • If a test step is Blocked, it should also be linked back to a defect • This will show the correlation between blocked test cases and defects • If there is an environment outage preventing testing, please notify Name / Emailimmediately • Testing resources should follow the guidelines listed in this presentation when it comes to Defect Severity, Test Case Status, processes, etc. • For any issues with accessing and setting up Quality Center, please contact Name / Email • If there are questions about specific processes within Quality Center (what a mandatory / optional field means and how /when it should be used, etc.) testing resources will contact the Testing Lead, Name / Email

  10. Defect Severity Guidelines • Defects will be categorized as follows:

  11. Defect Priority Guidelines • Defects will be categorized as follows:

  12. Defect and Re-test Assignment

  13. Test Case Status Definitions

  14. Test Ground Rules • All test cases should be executed directly into Quality Center • Test cases should not be executed in offline tools and later “mass updated” in Quality Center, as all metrics / reporting will be based real-time out of Quality Center • If you have issues accessing Quality Center, please reach out to Name / Emailto determine an alternate testing approach • Defects should be created directly from failed test steps within test cases and linked accordingly • This will show the correlation between failed test cases and defects • If a test step is Blocked, it should also be linked back to a defect • This will show the correlation between blocked test cases and defects • If there is an environment outage preventing testing, please notify Name / Emailimmediately • Testing resources should follow the guidelines listed in this presentation when it comes to Defect Severity, Test Case Status, processes, etc. • For any issues with accessing and setting up Quality Center, please contact Name / Email • If there are questions about CCM specific processes within Quality Center (what a mandatory / optional field means and how /when it should be used, etc.) testing resources will contact the Testing Lead, Name / Email

  15. Test Progress Example Overall Testing Progress Summary Statement Test Planning - Progress Test Planning - Summary Test Execution - Summary Test Execution - Progress

  16. Defects Summary Example Defects Summary Statement Defects - Progress Defects - Summary

  17. Priority 1 Outstanding Defects Priority 1 Defects Summary Statement

  18. Use Cases Execution Example Use Cases (Requirements) Summary Statement Use Cases - Progress Use Cases - Summary

More Related