December 10, 2012
Interim QA Lead: Joe Richards
Quality Assurance Kick-off Meeting
for the Orange County eFiling and eService Product
Agenda
• Quality Assurance Goal
• Tasks and Test Areas
• Team Roles and Responsibilities
• Testing Environment
• Test Processes
• Details and Project Snapshot
Goal
External Goal:
Ensure Rapid Legal’s OC eFiling and eService product
performs as expected and delivers customer
satisfaction.
Internal Goal:
Ensure quality assurance testing is performed with
excellence by the project team.
Tasks
• Unit Testing
• OC eFiling / eService Testing
• Existing Product Testing
• Regression Testing
• Corporate Website Testing
• User Acceptance Testing (Customers)
• Smoke Testing Pre/Post Production
• Product Verification
Areas
Customer Portal Gateway Lite Corporate Website
OC eFiling / eService Dashboard, Filter, Search Home Page
Existing Products OC eFiling / eService Overview Page
Manage Cases / Orders Administrative Pages OC eFiling / eService Login
New Case Accounting Pages Existing Products Login
Contact Us Maintenance Pages Pricing Deadlines and PDF
My Profile News
Alpha Customer Test FAQ
UAT Customer Test
Team Roles and Responsibilities
Task Assigned To:
Unit Testing Unit Testing
Customer Portal: OC eFiling / eService Customer Service
Corporate Website: OC eFiling / eService, Login Customer Service
Customer Portal: Manage Case / Orders Customer Service
Customer Portal: My Profile Customer Service
Customer Portal: Alpha Customer Testing Customer Service
Customer Portal: UAT Customer Testing Customer Service
Customer Portal: Existing Products Operations
Corporate Website: Existing Products, Login Operations
Gateway Lite: Dashboard, Filters and Search Operations
Gateway Lite: Order Flow Operations
Gateway Lite: Administration Operations, Accounting
Gateway Lite: Maintenance, Customers Team
Gateway Lite: Maintenance, All other menus Operations
Corporate Website: Content Stakeholders
Regression Testing: Customer Portal / Gateway Lite Team
Smoke Testing: Customer Portal / Gateway Lite / Corporate Website Team
Product Verification: Verify all Enhancements/Bugs Function Team
Testing Environments
Supported
Browsers
Supported Operating
Systems
Internet Explorer 9.0 Windows XP
Internet Explorer 8.0 Windows Vista
Firefox Windows 7
Google Chrome
Safari
IMPORTANT:
Email QA your available testing environments based on list below.
Test Processes and Confirmation
• Test Cases
– QA will define and distribute each teams detailed test cases.
• Test Procedure
– Perform test cases defined, using your own test case copy, track
your results.
• Problem Reporting
– Report errors using Team Foundation Server bug reporting.
Provide detailed steps taken to produce bug and if needed,
screen shots. When bug has been resolved, you will be
prompted to test functionality.
Details
• When does this QA Plan start? Today
• When do I get testing documents? Today
• Daily Expectation? 10 to 15 orders per day
• When does it end? Beyond our go Live date: 12/31/2012
Project Snapshot
Task Team Start Date End Date
Unit Testing Unit Testing 12/03/2012 12/11/2012
OC eFiling / eService Testing Customer Service 12/10/2012 12/28/2012
Existing Product Testing Operations 12/10/2012 12/28/2012
Corporate Website Testing Products Customer Service/Operations 12/12/2012 12/28/2012
Corporate Website Testing Content Stakeholders 12/12/2012 12/28/2012
Customer Testing Customer Service 12/17/2012 12/21/2012
Regression Testing Team 12/20/2012 12/21/2012
Smoke Testing Pre-Push Team 12/26/2012 12/28/2012
Smoke Testing Post-Push Team 12/29/2012 12/30/2012
Product Verification Team 12/29/2012 01/04/2013
Questions?

Ocqa kickoff meeting2012_12_10

  • 1.
    December 10, 2012 InterimQA Lead: Joe Richards Quality Assurance Kick-off Meeting for the Orange County eFiling and eService Product
  • 2.
    Agenda • Quality AssuranceGoal • Tasks and Test Areas • Team Roles and Responsibilities • Testing Environment • Test Processes • Details and Project Snapshot
  • 3.
    Goal External Goal: Ensure RapidLegal’s OC eFiling and eService product performs as expected and delivers customer satisfaction. Internal Goal: Ensure quality assurance testing is performed with excellence by the project team.
  • 4.
    Tasks • Unit Testing •OC eFiling / eService Testing • Existing Product Testing • Regression Testing • Corporate Website Testing • User Acceptance Testing (Customers) • Smoke Testing Pre/Post Production • Product Verification
  • 5.
    Areas Customer Portal GatewayLite Corporate Website OC eFiling / eService Dashboard, Filter, Search Home Page Existing Products OC eFiling / eService Overview Page Manage Cases / Orders Administrative Pages OC eFiling / eService Login New Case Accounting Pages Existing Products Login Contact Us Maintenance Pages Pricing Deadlines and PDF My Profile News Alpha Customer Test FAQ UAT Customer Test
  • 6.
    Team Roles andResponsibilities Task Assigned To: Unit Testing Unit Testing Customer Portal: OC eFiling / eService Customer Service Corporate Website: OC eFiling / eService, Login Customer Service Customer Portal: Manage Case / Orders Customer Service Customer Portal: My Profile Customer Service Customer Portal: Alpha Customer Testing Customer Service Customer Portal: UAT Customer Testing Customer Service Customer Portal: Existing Products Operations Corporate Website: Existing Products, Login Operations Gateway Lite: Dashboard, Filters and Search Operations Gateway Lite: Order Flow Operations Gateway Lite: Administration Operations, Accounting Gateway Lite: Maintenance, Customers Team Gateway Lite: Maintenance, All other menus Operations Corporate Website: Content Stakeholders Regression Testing: Customer Portal / Gateway Lite Team Smoke Testing: Customer Portal / Gateway Lite / Corporate Website Team Product Verification: Verify all Enhancements/Bugs Function Team
  • 7.
    Testing Environments Supported Browsers Supported Operating Systems InternetExplorer 9.0 Windows XP Internet Explorer 8.0 Windows Vista Firefox Windows 7 Google Chrome Safari IMPORTANT: Email QA your available testing environments based on list below.
  • 8.
    Test Processes andConfirmation • Test Cases – QA will define and distribute each teams detailed test cases. • Test Procedure – Perform test cases defined, using your own test case copy, track your results. • Problem Reporting – Report errors using Team Foundation Server bug reporting. Provide detailed steps taken to produce bug and if needed, screen shots. When bug has been resolved, you will be prompted to test functionality.
  • 9.
    Details • When doesthis QA Plan start? Today • When do I get testing documents? Today • Daily Expectation? 10 to 15 orders per day • When does it end? Beyond our go Live date: 12/31/2012
  • 10.
    Project Snapshot Task TeamStart Date End Date Unit Testing Unit Testing 12/03/2012 12/11/2012 OC eFiling / eService Testing Customer Service 12/10/2012 12/28/2012 Existing Product Testing Operations 12/10/2012 12/28/2012 Corporate Website Testing Products Customer Service/Operations 12/12/2012 12/28/2012 Corporate Website Testing Content Stakeholders 12/12/2012 12/28/2012 Customer Testing Customer Service 12/17/2012 12/21/2012 Regression Testing Team 12/20/2012 12/21/2012 Smoke Testing Pre-Push Team 12/26/2012 12/28/2012 Smoke Testing Post-Push Team 12/29/2012 12/30/2012 Product Verification Team 12/29/2012 01/04/2013
  • 11.