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.
 Software Quality Assurance

“Project Name” Test Plan

Created By Revision Creation date Last Update Page
FOQA 1.0 Nov 13-2009 Nov 13-09 2/5

ROLES AND RESPONSIBILITIES

Below each role and its responsibilities are detailed:
Role Activity Details
Delivers:
User requirements / histories Requestor could be (only one) of:
Technical documentation
List of features
List of components • FO Solution Manager
Requestor
• Configuration/Usability sequence • Project Manager

• Approves Test cases • System / Business Analyst

o Functional Test cases
• Global Implementor
o List of functions to be tested
using automated tools (if Sanity • Medical Compliance Team
Test service is requested)
• Test cases creation (apply when
Medical Compliance is the requestor)
• Project kick off
Defines Stop Test/Fail Cliteria PM could be (only one) of:
• Defines Meaning of Severities
o The meaning of severities: • FO Solution manager
Project o Critical • Global Implementator
Manager o Major
o Normal
o Minor
o Enhancement
• Validate (reject/assign) reported
issues in Bugzilla.
• Project closure

• Creates/Updates Product in
Bugzilla
• Creates Project/Update project
structure in QA Director
• QA coordinators create new
• Creates Test Plan (get Test Plan projects / versions /
QA Engineer approval from Requestor) components in Bugzilla.
• Creates Test Cases / Automated
visual scripts
• Setup Test Environment
• Executes Test
• Logs bugs/findings into Bugzilla
• Delivers Test Report
Delivers:
• Installation package • New features demo provided
Developer • Release notes by Development team takes
place once a new/updated
• Fixes reported issues functionality is completed.
• Set “Resolved” status in Bugzilla
 Software Quality Assurance

“Project Name” Test Plan

Created By Revision Creation date Last Update Page
FOQA 1.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.
• Type of service (Sanity Test, Functional Test, Regression Test, etc).
• 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, technical
requirement, user histories and developers (SRS) at defined source (such as Xplanner, ChangeLog), etc).

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.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, Functional Test, Regression Test,
etc).

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 Test plan

project

Request for
requirement detail

Provide Provide application

requirement detail detail

Test case
Create test case

Get test case

approval

Review and
approve test case

Execute test

Generate test Test report

report
Repeatable

Initiate release
meeting