Esker Quality Assurance Process

February QAI Meeting

Tracy Donohue, Quality Assurance Manager

February 7, 2001

Agenda

BackgroundQA processChallenges

Background

Persoft—PC-to-Host—Web-to-Host

Acquired by Esker (1999)—PC-to-Host—Web-to-Host—Fax

Connectivity Products

Shrink-wrapped softwareFortune 1000 customers“Out of the box” solutions

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.”

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

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

QA Process

The BIG picture

QAR&D

Tech Writing

PM

Tech Support

Marketing

QA

R&DTech Writing

QA Process

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

Challenges

Global companyGlobal Software and Development

—New tools needed, possibly—Maintain “best practices”—Work as a team

Communication—New tools needed, possibly—More face to face contact

Questions?