Thursday, November 18, 2010

Agile Testing with HP Quality Center Agile Accelerator

What is Agile testing?

Agile testing is a software testing practice that follows the principles of the agile manifesto, emphasizing testing from the perspective of customers who will utilize the system. Agile testing does not emphasize rigidly defined testing procedures, but rather focuses on testing iteratively against newly developed code until quality is achieved from an end customer's perspective. In other words, the emphasis is shifted from "testers as quality police" to something more like "entire project team working toward demonstrable quality."

Agile testing involves testing from the customer perspective as early as possible, testing early and often as code becomes available and stable enough from module/unit level testing.

Since working increments of the software are released often in agile software development, there is also a need to test often. This is commonly done by using automated acceptance testing to minimize the amount of manual labour involved. Doing only manual testing in agile development may result in either buggy software or slipping schedules because it may not be possible to test the entire build manually before each release.

HP Quality Center Agile Accelerator

The HP Quality Center Agile Accelerator is designed to help projects manage Agile development using HP Quality Center 10.0. It can be imported into HP Quality Center 10.0 as a base project to manage both development and testing efforts within the same HP Quality Center Project. It comes with pre-built Agile user roles and related privileges, pre-defined Agile process workflows, configurations and rules to help you manage projects driven by Agile methodology. It also facilitates Agile reporting allowing you to track progress burn-down, burn-up and velocity.

Agile Accelerator Benefits
  • Supports multiple Agile practices including Scrum/XP methodology: Sprint, Backlog, User story
  • Reduces calculation effort including tasks, estimation, planning, and spent hours
  • Improves information visibility across all user groups such as product managers, project engineers, Scrum Master, and others.
  • Encompasses the full project lifecycle from planning to delivery, development and testing ensuring application meets promised requirements
  • Reports project progress and delivered value through Burn-up charts and Burn-down charts

No comments: