1 / 11

Esker Quality Assurance Process

This document summarizes the key points discussed in the February 2001 Quality Assurance Initiative (QAI) meeting led by Tracy Donohue, Quality Assurance Manager at Esker. It covers the QA process, challenges faced with products such as Persoft and fax connectivity solutions post-Esker acquisition, and outlines the roles of the core team comprised of R&D, QA, Tech Writing, Tech Support, Product Management, and Marketing. The meeting emphasized the importance of specifications, testing strategies, and tools to maintain best practices in a global software development environment.

todd-roy
Télécharger la présentation

Esker Quality Assurance Process

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. Esker Quality Assurance Process February QAI Meeting Tracy Donohue, Quality Assurance Manager February 7, 2001

  2. Agenda • Background • QA process • Challenges

  3. Background • Persoft • PC-to-Host • Web-to-Host • Acquired by Esker (1999) • PC-to-Host • Web-to-Host • Fax

  4. Connectivity Products • Shrink-wrapped software • Fortune 1000 customers • “Out of the box” solutions

  5. QA Process • Product Plan • Core Team • A group of people that work together to design a new feature • R&D, QA, Tech Writing, Tech Support, Product Management, Marketing • Specifications • “Testing against a specification is like walking on water. It helps if it’s frozen.”

  6. QA Process • Product Plan -> Testing Strategy/Plan • Provides an overall plan tailored to the testing needs of the project. • Preliminary Schedule • Core Team -> Test Outline • Detailed document that is used to test the features of the product • Functional, Limits and Boundaries, Compatibility • Reviewed by developer

  7. QA Process • Alpha Phase • File set integrity • New features • High level acceptance testing • Bug Ranking (1’s and 2’s) • Beta Phase • Customer’s and potential customers test • Real world application testing • Integration testing • Regression, Functional, Load, Compatibility, Performance • Documentation review

  8. QA Process • The BIG picture Development Cycle Core Team QA R&D QA Tech Writing Tech Writing R&D PM Tech Support Marketing Ship

  9. QA Process • Tools & Best Practices • Core Teams • Bug Tracking System • Bug Ranking Meetings • Automated Tests • High Level Acceptance Testing • Drive Images, “clean machine”

  10. Challenges • Global company • Global Software and Development • New tools needed, possibly • Maintain “best practices” • Work as a team • Communication • New tools needed, possibly • More face to face contact

  11. Questions?

More Related