Software Quality Assurance Process

How the entire Quality Assurance Process is being carried out in a company (i.e.) in
practical environment?.

Prepared By
Bala K
QA Analyst
How the entire Quality Assurance Process is being carried out in
TWC (i.e) in practical environment?
How the entire Quality Assurance Process is being carried out in
TWC(i.e) in practical environment?
 Here I focus on software Testing actual
working process. We have got a good experience of
software Quality Assurance related activities.  So
I will try to share more practically rather than
theoretically.
 Whenever we get any new project there is initial
project familiarity meeting. In this meeting we
basically discuss on who is client? what is project
duration and when is delivery? Who is involved in
project i.e. manager, Tech leads, QA leads,
developers, testers etc..?


How the entire Quality Assurance Process is being carried
out ina company (i.e) in practical environment?


 From the SRS (software requirement
specification) project plan is developed. The
responsibility of testers is to create
Software Test Plan from this SRS and project
plan. Developers start coding from the design.
The project work is divided into different
modules and these project modules are
distributed among the developers. In meantime
testers responsibility is to create
Traceability Matrix test scenario and write
Test Cases according to assigned modules. We
try to cover almost all the functional test
cases from SRS.  The data can be maintained
manually in some excel test case templates or
bug tracking tools.
How the entire Quality Assurance Process is being carried out in
a company (i.e) in practical environment?
 When developers finish individual modules, those
modules are assigned to testers.  Smoke testing
is performed on these modules and if they fail
this test, modules are reassigned to respective
developers for fix. For passed modules manual
testing is carried out from the written test
cases. If any Bug is found that get assigned to
module developer and  get logged in
Defect Tracking Template. On bug fix tester do
bug verification and regression testing of all
related modules. If bug passes the verification
it is marked as verified and marked as closed.
Otherwise above mentioned bug cycle gets
repeated.(I will cover bug life cycle in other
post)
How the entire Quality Assurance Process is being carried
out in a company (i.e) in practical environment?
 Different tests are performed on individual
modules and integration testing on module
integration. These tests includes Compatibility
testing i.e. testing application on different
hardware, OS versions,  software platform,
different browsers etc. Load and stress testing
is also carried out according to SRS. Finally
system testing is performed by creating virtual
client environment. On passing all the test cases
Test Report is prepared and decision is taken to
release the product!

Let’s take a look how testing is carried out in the already
existing System (Vendor Product).
Let’s take a look how testing is carried out in the
already existing System (Vendor Product).
 Methodology of Product Quality Assurance
developed by a Vendor .


 PPQA audits With the

help of SRS :
 Peer Reviews with the
help of SRS :
 Validation testing :
 Data Driven Testing :
 Load / Stress testing :
 Compatibility testing :
 Usability testing :

Let’s take a look how testing is carried out in the New
Systems (Developing from Scratch)
 Let’s take a look how testing is carried out in the New
Systems (Developing from Scratch)
A good test plan is the cornerstone of a successful testing implementation .
While every testing effort may be unique , most test plans include a common content framework . This article
presents the components that make up this framework , and serves as a guide to writing your own test plan .

 Requirements
This section of the test plan lists all requirements to be tested.


 Functional Test Requirements – Enlist the functions to be tested.

 Design Requirements - Testing the user interfaces.
 Integration Requirements - the requirements for testing the flow of data from
one component to the other may be included if it will be part of the test plan.


 Test Strategy
This Section will describe how the test objectives will be met for each type of testing


 Objective
 Technique
 Traceability Matrix
 Test Cases
 Risks / Assumptions
 Tools
 Resources
Identify the resource roles and responsibilities that will be required for test plan execution.


  Project Plan - develop a project plan showing the phases, tasks, and
resources.
 Let’s take a look how testing is carried out in the New
Systems (Developing from Scratch)
 Schedule
 Document the schedule in which the application under test is to be made
available for testing, and the estimated time for executing test cases.


 Deliverables
 List all the deliverables that are associated with the testing effort, and
where copies of these deliverables or documents may be located.


 Defect Tracking and Reporting - Describe any ratings, categories or

classifications used to identify or prioritize defects.
 Criti cal
 Sever e
 High
 Cosme tic


 Approval - The test plan should be reviewed by all parties responsible for its
execution, and approved by the test team, product and development managers.


 Results - When the test effort is complete, document the results.

 n with the Help of Software Requirement Specification (SRS) or Functional Specification Document (FDS)
QA Process life Cycle Diagram
Lets take a look, How the Testing is Carried out Practically.
Inputs : Project Plan

Inputs : SRS & FDS

CLOSED

Pass

Fail

Retest (Regression
Testing)

Track it to the Developer for Fix

Is Fixed
System Integration with Automated Functional Testing
Tool.
Once the Application/Modules/Screens are being Freeze by Manual Testing, then Integrate the Application Automated.

Regression Testing
Do the Above Steps Regressively, in order to Check the Application more and more for both Tested as well as
untested Modules
Quality Guarantee Certification