Know your

The Methodology:

CÖRR is a best practice testing methodology separated into four stages.  The need for CÖRR followed the release of ZĀTO 2.0 in March 2013 as a way to ensure customer’s success in implementation of the HP ALM Suite with SAP TAO.  While CÖRR was originally developed for SAP, it has been expanded to encompass any testing initiative whether it is manual, or automated.  CÖRR is the structured methodology when using HP Application Lifecycle Management (ALM) suite for testing.

All good methodologies rely on knowing the most important processes and data to CAPTURE.  Structuring the captured information in a way that ensures both short-term and long-term success is what the C in CÖRR is all about.  Knowing how to OPTIMIZE your testing architecture to streamline your projects while delivering results in your given framework is the next step for securing your QA vision.  REPORTING is critical to any project.  Being able to have usable dashboard sand critical reports that include historical information is why Assure’s TotalView is the only choice for a true CÖRR ALM environment.  When considering ROI, QA departments look at calculating ROI for the tools that help them test. While this is important, it is even more critical that QA is focused on the ROI that the team brings to the project.  Having CÖRR will continue to demonstrate the value QA brings to the table, project after project.

What is CÖRR?

  • C - Capture
  • Ö - Öptimize
  • R - Report
  • R - ROI


The starting point for any customer that is planning on using HP ALM for testing, requires that the CÖRR Foundation be in place.  Whether testing manualy, automated testing, or testing SAP with TAO; securing your QA practices with CÖRR is critical to your success. Focusing on installing controls to give QA the ability to oversee the assets being built.  It does not matter if they are built by the direct team, or third party resources, even resources from the line of business, CÖRR gives you the key to become successful.

The CÖRR foundation is collection of software and best practices to enable customers to achieve success in testing.  CÖRR foundation uses Warde Associates best practice methodology to secure QA vision in testing.  The Foundation Consists of:

  • HP ALM best practices document designed to support CÖRR across all ALM modules
  • Warde Associates ZĀTO
  • Assure's TotalView

No matter what application your testing it all begins with a solid CÖRR.



Any methodology needs to address the issue of what do I test.  Over 20% of the typical business transactions complete 80% of the business activity.  Knowing how to ensure the correct processes are tested is what this phase offers customers.

Business Requirement traceability is typically overlooked as QA focuses on test requirements.  While test requirements are important, understanding how the business is affected and the true cost of business process downtime becomes clear to the customer.  Having ALM configured to not only support ongoing regression testing for the changes that seem to make it to production daily, but also how to manage testing that is project based is the true focus of this phase.

For our SAP customers, we also help them implement the SAP Solution Manager to Quality Center adapter for their ALM environment.  Having this extra level of interoperability allows customers the ability to reduce redundancy and recognize what is being developed, giving QA a jump-start in optimizing their assets.


Everything changes.  Nothing strikes fear into a QA director more than trying to understand if the errors that are being reported are due to a true change or a potential defect.  In this phase a customer is educated on how to manage this change recognizing what moving assets means from project development to regression.  Regression strategies are also discussed and mapping out the best use-case for the specific company is the goal.

For our SAP customers, we go a step further and educate the customer on SAP Solution Manager’s Business Process Change Analyzer (BPCA).  Customers may not understand that they already own this tool, so we explain how it can truly be leveraged and explain the integrated functionality that SAP TAO beings to the table. This functionality not only helps SAP TAO fix its own scripts, but it also helps customers stay current with not only their automation, but also with their Technical Bill of Materials (TBOMs).  This maintenance of TBOMs is the most often overlooked step by customers to keep BPCA working effectively.


Having the correct data in your test environment is absolutely critical to the success of a testing practice.  Since the other levels of CÖRR have been applied, we can now focus on the last obstacle.  Addressing different strategies on how to address the data issue in QA from restoring, copying fresh, or building data, are fully covered.  Additionally, other environments, such as training are considered in the overall strategy for the customer moving them closer to true Enterprise Integration.

For our SAP customers, we also take it a step further to talk about the Test Data Migration Server (TDMS) tool from SAP and the different use cases that the functionality of TDMS provides.