Regression testing is any type of software testing that seeks to uncover software errors

by partially retesting a modified program. The intent of regression testing is to assure that
a bug fix has been successfully corrected based on the error that was found, while
providing a general assurance that no other errors were introduced in the process of fixing
the original problem. Regression is commonly used to efficiently test bug fixes by
systematically selecting the appropriate minimum test suite needed to adequately cover
the affected software code/requirements change. Common methods of regression testing
include rerunning previously run tests and checking whether previously fixed faults have
re-emerged.

"One of the main reasons for regression testing is that it's often extremely difficult for a
programmer to figure out how a change in one part of the software will echo in other
parts of the software."[1]

Contents
[hide]

• 1 Background
• 2 Uses
• 3 See also
• 4 References

• 5 External links

[edit] Background
Experience has shown that as software is fixed, emergence of new and/or reemergence of
old faults is quite common. Sometimes reemergence occurs because a fix gets lost
through poor revision control practices (or simple human error in revision control). Often,
a fix for a problem will be "fragile" in that it fixes the problem in the narrow case where
it was first observed but not in more general cases which may arise over the lifetime of
the software. Frequently, a fix for a problem in one area inadvertently causes a software
bug in another area. Finally, it has often been the case that when some feature is
redesigned, the same mistakes that were made in the original implementation of the
feature were made in the redesign.

Therefore, in most software development situations it is considered good practice that

when a bug is located and fixed, a test that exposes the bug is recorded and regularly
retested after subsequent changes to the program. Although this may be done through
manual testing procedures using programming techniques, it is often done using
automated testing tools. Such a test suite contains software tools that allow the testing
environment to execute all the regression test cases automatically; some projects even set
up automated systems to automatically re-run all regression tests at specified intervals
and report any failures (which could imply a regression or an out-of-date test). Common
strategies are to run such a system after every successful compile (for small projects),
every night, or once a week. Those strategies can be automated by an external tool, such
as BuildBot.

Regression testing is an integral part of the extreme programming software development

method. In this method, design documents are replaced by extensive, repeatable, and
automated testing of the entire software package at every stage in the software
development cycle.

Traditionally, in the corporate world, regression testing has been performed by a software
quality assurance team after the development team has completed work. However,
defects found at this stage are the most costly to fix. This problem is being addressed by
the rise of developer testing. Although developers have always written test cases as part
of the development cycle, these test cases have generally been either functional tests or
unit tests that verify only intended outcomes. Developer testing compels a developer to
focus on unit testing and to include both positive and negative test cases.[2]

[edit] Uses
Regression testing can be used not only for testing the correctness of a program, but often
also for tracking the quality of its output. For instance, in the design of a compiler,
regression testing should track the code size, simulation time and time of the test suite
cases.

HP Quality Center
From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article may need to be wikified to meet Wikipedia's quality standards.
Please help by adding relevant internal links, or by improving the article's layout.
(January 2009)
This article may not meet the general notability guideline. Please help to establish
notability by adding reliable, secondary sources about the topic. If notability
cannot be established, the article is likely to be merged, redirected, or deleted.
(January 2009)
This article needs references that appear in reliable third-party publications.
Primary sources or sources affiliated with the subject are generally not sufficient
for a Wikipedia article. Please add more appropriate citations from reliable
 sources. (January 2009)
HP Quality Center
Developer(s) HP/Mercury Interactive
Stable release 10.0
Operating system Microsoft Windows
Development status Active
Type quality management
License Proprietary
Website HP Quality Center

HP Quality Center (QC) (formerly HP TestDirector for Quality Center) is a web

based Test Management Tool by Mercury Interactive (now HP). It is based on Client
Server technology and has five main modules/tabs: Releases, Requirements, Test Plan,
Test Lab and Defects for management of testing processes. There can be additional
modules as well depending on the various Add ins installed like BPT (Business Process
Testing) etc.

Contents
[hide]

• 1 Modules
o 1.1 Releases
o 1.2 Requirements
o 1.3 Test Plan
o 1.4 Test Lab
o 1.5 Defects
• 2 Versions of Quality Center

• 3 External links

[edit] Modules
[edit] Releases

This module helps to manage releases and cycles (iterations) more effectively. User can
easily plan and track application release progress using this module.
[edit] Requirements

This module is used for Requirement Management and Requirements Traceability of

various Test cases stored in the QC Repository.

[edit] Test Plan

This tab is used for creating or updating different Test Cases. The Test Cases are
contained in different folders which are displayed in a tree like structure. It can store both
Manual as well as Automated test cases. Manual Test Cases can be written locally or
imported from Excel Sheets. With each 'Test Step' having Expected Result and
ActualResult section. QC supports automated script developed for different Automation
Tools like QTP, LoadRunner, WinRunner etc. These scripts can be saved directly from
the Tool into the Test Plan tab of QC. However, prior to this, appropriate QC Add-in
needs to be installed to support an Automation Tool.

[edit] Test Lab

This tab is for execution of the test cases stored in the Test Plan module which can be
imported locally to the Test Lab screen and Run. When Manual Test case is executed, it
opens up a pop up listing all the Test Steps and the user is supposed to update status of
each step with Passed, Failed or Not Complete. When automated test case is run, QC
invokes the Automation Tool which in turn executes the script and stores back the result
into QC repository and displays on the UI.

[edit] Defects

All the defects are logged in this tab of Quality Center. These defects can be mapped to
the corresponding test cases which failed and hence to the Requirements tab.

[edit] Versions of Quality Center

1. 10.0
2. 9.2
3. 9.0 - released in 2006
4. 8.2
5. 8.0
can you meet your quality
management challenges?
Consider the typical quality assurance (CQA) organization.
It uses stand-alone documents or a collection of
disparate systems to keep track of its quality and testing
efforts and assets. This can result in:
• Inefficient and redundant testing due to missing
information, ineffective communication and a lack
of consistent and repeatable processes
• Increased risk of deploying a bad application
•User frustration with disorganization, shifting priorities
and rushed deadlines
•Many hours spent compiling reports that are immediately
out of date
• Inadequate visibility into project progress and status,
resulting in last-minute crunches, missed deadlines
and poor quality
In addition, the work of a typical QA organization
is slowed by manual test methods used to functionally
validate applications before they go live. Manual testing
simply cannot keep up with the demand and complexity
of today’s multi-tiered, multi-platformed, business
service-oriented applications.
HP Quality Center is designed to address these wideranging
challenges—and help you turn quality into
a competitive advantage.
HP Quality Center
With HP Quality Center, you have a global platform that:
• Provides real-time visibility of requirements coverage
and associated defects to paint a clear picture of
business risk
• Enables your organization to manage the release
process and make more informed release decisions
with real-time KPIs and reports
•Helps your managers measure progress and effectiveness
of quality activities
•Allows your QA teams, developers and business
analysts to collaborate in the quality lifecycle with
a single global platform
• Enables your organization to centrally manage
manual and automated testing assets
HP Quality Center manages and governs quality
processes and automates software testing across
your application environment. It arms you
with the capabilities you need to manage the
release process and make more informed
release decisions.
HP Quality Center
Combine requirement, test and defect management
into a single quality platform.
BTO: Optimize the business
outcome of IT
HP Quality Center is a key
component of the HP Business
Technology Optimization (BTO)
strategy. BTO helps you make
sure that every dollar invested
in IT, every resource allocated,
and every application in development
or production meets your
business goals.
Unlike software offerings and
methodologies that focus only
on internal IT processes, HP BTO
optimizes the strategic functions
between technology and business.
Our lifecycle approach enables
your organization to align IT with
business priorities and to deliver
increased value from end to end.
4AA0-9587ENW Rev. 1, January 2007
To learn more, visit: www.hp.com/go/software
© Copyright 2006, 2007 Hewlett-Packard Development Company, L.P. The information contained herein is
subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting
an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California.
• Facilitates standardized testing and quality processes
that boost productivity through workflows and alerts
•Allows your organization to lower costs by capturing
critical defects before they reach production
By using consistent, repeatable and standardized
processes, HP Quality Center can help you reduce
costs and risk, increase quality and produce more
frequent releases.
HP Quality Center components
The HP Quality Center Foundation is an enterprise-level
J2EE platform that serves as a central repository for all
quality assets, houses centralized workflow rules and
facilitates collaboration among all parties involved in
the quality process. In addition, HP Quality Center
includes dashboard technology that provides an
executive-level view of the entire quality process.
HP TestDirector for HP Quality Center software includes
requirements management, test plan, test lab and
defect management modules. It offers a seamless,
consistent and repeatable process for all stages of
application quality management—from gathering
requirements, to planning and scheduling tests,
analyzing results, and managing defects and issues.
Functional test components include HP QuickTest
Professional and HP WinRunner software. QuickTest
Professional is an advanced automated testing solution
for building functional and regression tests. WinRunner
is the standard functional testing solution for enterprise
IT applications.
HP Business Process Testing software brings business
analysts and SMEs into the process of defining business
use cases and process flows to increase the accuracy of
tests and help align testing to business outcomes. Based
on the defined business processes, the test engineer can
then create reusable test components using both manual
and automated methods and share them with distributed
quality teams in a single web-based QC repository.
Extensions for SAP and SOA provide out-of-the box capabilities
for SAP, SOA and Oracle® quality management.
Quality teams can focus testing on the business processes
impacted by changes—so applications are released with
increased quality and a reduced level of risk.
HP Service Test components enable effective quality management,
including SOA test management, requirements,
defects tracking, functional testing, regression testing and
business process design validation.
Why HP?
HP is ideally positioned to meet your most stringent
quality management needs. We offer:
Market leadership—We have a 56.8 percent market
share in distributed automated software quality,
according to IDC.
Integrated approach—Our solutions for quality
management work together across the application
lifecycle, spanning IT applications and IT operations.
Enterprise ready—Unmatched scalability and
enterprise architecture make HP Quality Center the
solution of choice for centralization and standardization
initiatives.
HP Quality Center
HP Quality Center brings together key elements of quality
management and functional testing
into a single quality platform.
Dashboard
HP Quality Center
Foundation
Functional Testing Business Process Testing
1.Requirements Management
2 Test Plan
3 Test Lab
4 Defect Management
5 Extensions
SAP, SOA

HP Quality Center
HP Quality Center brings together key elements of quality
management and functional testing
into a single quality platform.
Dashboard
HP Quality Center
Foundation
Functional Testing Business Process Testing
Requirements
Management
Test Plan Test Lab
Defect
Management
Extensions
SAP, SOA
Functional Testing , Business Process Testing