Software Quality Assurance “Project Name” Test Plan Created By

Revision

Creation date

Last Update

Page

FOQA

1.0

Nov 13-2009

Nov 13-09

1/5

FOQA process

OBJECTIVE
This document explains the process in detail that FOQA will follow for all projects.

• Project closure • • Creates/Updates Product in Bugzilla Creates Project/Update project structure in QA Director Creates Test Plan (get Test Plan approval from Requestor) Creates Test Cases / Automated visual scripts Setup Test Environment Executes Test Logs bugs/findings into Bugzilla Delivers Test Report Delivers: Installation package Release notes Fixes reported issues Set “Resolved” status in Bugzilla PM could be (only one) of: • • FO Solution manager Global Implementator QA Engineer • • • • • • • QA coordinators create new projects / versions / components in Bugzilla.0 Nov 13-2009 Nov 13-09 2/5 ROLES AND RESPONSIBILITIES Below each role and its responsibilities are detailed: Role Activity Delivers: User requirements / histories Technical documentation List of features List of components • Configuration/Usability sequence • Approves Test cases o Functional Test cases o List of functions to be tested using automated tools (if Sanity Test service is requested) Test cases creation (apply when Medical Compliance is the requestor) Details Requestor could be (only one) of: • • • • • FO Solution Manager Project Manager System / Business Analyst Global Implementor Medical Compliance Team Requestor • Project Manager • Project kick off Defines Stop Test/Fail Cliteria • Defines Meaning of Severities o The meaning of severities: o Critical o Major o Normal o Minor o Enhancement • Validate (reject/assign) reported issues in Bugzilla. . Developer • • • • • New features demo provided by Development team takes place once a new/updated functionality is completed.Software Quality Assurance “Project Name” Test Plan Created By Revision Creation date Last Update Page FOQA 1.

etc). technical requirement. user histories and developers (SRS) at defined source (such as Xplanner. • Type of service (Sanity Test. Functional Test. etc). Regression Test.0 Nov 13-2009 Nov 13-09 3/5 Test Plan QA Team uses a Standard Test Plan template for each project being tested where the test description is agreed. • Environment setup o Servers name o DB connection settings o Web links o Etc • Start – End dates for testing • Etc (see test Plan template) Test plan is delivered by QA team and approved by Requestor/Project Manager before tests are executed. Test Plan Template can be found in the following link: << Add link to Standard Test plan>> Test Cases QA team creates test cases based on the documentation provided by the Requestor (functional requirement. ChangeLog). Test Cases are created inside QA Director (http://sacnt366/qadirector/) by following the standards defined in <<link to standards in QA Director>> The following image is an example of a group of test cases in QA Director: .Software Quality Assurance “Project Name” Test Plan Created By Revision Creation date Last Update Page FOQA 1.

Regression Test.0 Nov 13-2009 Nov 13-09 4/5 The following image is an example of a test case in QA Director: Test report QA Team uses a Standard Test Report template for all services provided (Sanity Test.Software Quality Assurance “Project Name” Test Plan Created By Revision Creation date Last Update Page FOQA 1. etc). Functional Test. Test report is delivered by QA team to Requestor/Project Manager at the end of each test. Test Report Template can be found in the following link: << Add link to Standard Test plan>> QA Process Flow .

Software Quality Assurance “Project Name” Test Plan Created By Revision Creation date Last Update Page FOQA 1.0 Nov 13-2009 Nov 13-09 5/5 FOQA General Process Requestor PM QA Dev Deliverable Initiate project to team Plan for test project Test plan Request for requirement detail Provide requirement detail Create test case Provide application detail Test case Get test case approval Review and approve test case Execute test Generate test report Repeatable Test report Initiate release meeting .

Sign up to vote on this title
UsefulNot useful