Quality

Assurance
P. Srinivas

Agenda
What is QC?
What is QA?
Cost of Quality
What is Software QA?

SQL Activities
Software Reviews
Cost Impact of Software Defects
Defect Amplification and Removal

Software Testing of DW Projects

Test case/(s) creation

Upload into Project folder of HP Quality Center
Create Test data for the scenarios mentioned
Execute the test results and capture in HPQC
Generate a report and send for review

What is quality?
As per Robert Glass [GLA98] said that
User satisfaction = Compliant Product + [Good Quality]
+ [delivery within budget and schedule]

What is Quality Control?

The QC means A series of inspections, reviews, and tests
Performed and recorded throughout the Engineering/
Non Engineering process to ensure each work product meets the
requirements placed.

What is Quality Assurance?

Quality Assurance consists of a set of auditing and reporting

Functions that assesses the effectiveness and completeness
Of quality control activities.
The goal is to remove the errors, defects, bugs or faults which are
Synonyms in general.
What is Cost of Quality?
The Cost of Quality includes all the costs incurred in the
Pursuit of a better product to customers.

What are the costs of Quality(COQ)?

There are three types of COQ

Prevention costs
Appraisal costs
Failure costs
Preventive costs are Quality planning, formal technical reviews,
Test equipment and training.
Appraisal costs include activities to gain insight into product
condition the first time through each process
Failure costs are broadly classified as internal failure costs
and external failure costs

Software Quality Assurance

Software Quality is defined as

Conformance to explicitly stated functional and performancerequirements, explicitly documented development standards,and implicit characteristics that are expected at all professionallydeveloped software.

SQA Activities
Broadly there will be two groups where one group do work on
technical work and other group works on quality Assurance
planning, oversight, record keeping, Analysis and reporting.

Testing life cycle

Gant chart for tasks to be performed

Network diagram of a project

What is white box testing?

Test cases may be written by using
1)Guarantee that all independent paths within
a module
have been executed at least once
2)Exercise all logical decisions on their true
and false sides,
3)Execute all loops at their boundaries and
within their
operational bounds, and
4)Exercise internal data structures to ensure
their validity.

What is Black box testing?

Let us not confuse with Aeroplane black box! Rather its a jargon
Which is used in Software Engineering.
Without seeing the code, write test cases. It is done purposely to
Know the behaviour of the code.
Once the black box testing is over, Integration testing will take place
And later the Performance or Load test will be done to see whether
The operation is in permissible limits
but with checks and balances we prefer this lengthy procedure.

What is test strategy documentation?

A Test Strategy document is a high level document and normally
developed by project manager. This document defines
Software Testing Approach to achieve testing objectives.
The Test Strategy is normally derived from the Business Requirement
Specification document.
The Test Strategy document is a static document meaning that
it is not updated too often. It sets the standards for testing
processes and activities and other documents such as the Test Plan
draws its contents from those standards set in the Test Strategy
Document.

I had the opportunity to write for one project!!

Components of the Test Strategy document

Introduction
Scope
Business issues
Roles and responsibilities
Communication and status reporting
Test deliverables
Industry standards to follow
Test automation and tools
Testing measurements and metrics
Known Risks
Unknown Risks
Mitigation Plan
Defect reporting and tracking
Change and configuration management
Training plan
Lessons learnt

What is a test plan?

The Test Plan document on the other hand, is derived from the
Product Description, Software Requirement Specification SRS,
or Use Case Documents.
The Test Plan document is usually prepared by the Test Lead or
Test Manager and the focus of the document is to describe
what to test, how to test, when to test and who will do what test.
It is not uncommon to have one Master Test Plan which is a
common document for the test phases and each test phase
have their own Test Plan documents

Components of the Test Plandocument

Test Plan id
Introduction
Test items
Features to be tested
Features not to be tested
Test techniques
Testing tasks
Suspension criteria
Features pass or fail criteria
Test environment (Go-No Go criteria, Entry
criteria, Exit criteria)
Test deliverables
Customers/Stakeholders list email addresses
Staff and training needs
Responsibilities
Schedule

What is a test case?

A test case will have test steps (How-to) which will help to log the
Details after execution of tests in HPQC
For every project depending on the functionality or script, the test
Cases with test steps are created.
Generally there will be Bugs reporting and tracking system will
Be in place to report the defects and clarity mails e.t.c.,
Now, The Mercury Quality center was taken over by HP
and the name was changed to HPQC

What is smoke test in software engineering?

In computer programming and software testing, smoke testing

is preliminary testing to reveal simple failures severe enough to
reject a prospective software release.
A smoke tester will select and run a subset of test cases that
cover the most important functionality of a component or
system, to ascertain if crucial functions of the software work
correctly. When used to determine if a computer program
should be subjected to further, more fine-grained testing,
a smoke test may be called an intake test.

Regression testing
Regression testing is a type of software testing that verifies
that software previously developed and tested still
performs correctly even after it was changed or interfaced
with other software. Changes may include software
enhancements, patches, configuration changes, etc. During
regression testing, new software bugs or regressions may
be uncovered. Sometimes a software change impact
analysis is performed to determine what areas could be
affected by the proposed changes. These areas may
include functional and non-functional areas of the system.

Integration testing
Integration testing is the phase in software testing in which
individual software modules are combined and tested as a
group. It occurs after unit testing and before validation
testing. Integration testing takes as its input modules that
have been unit tested, groups them in larger aggregates,
applies tests defined in an integration test plan to those
aggregates, and delivers as its output the integrated system
ready for system testing.

Login page for HPQC

Any Questions!!!