EGI Quality Control

From EGIWiki
Revision as of 18:23, 18 February 2011 by Michel (talk | contribs) (Created page with '{{Tech menubar}} {{TOC_right}} Where Quality Assurance aims to capture and describe the quality that any software delivered to EGI must meet, Quality Control ensures that the so…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Technology Software Component Delivery Software Provisioning UMD Middleware Cloud Middleware Distribution Containers Distribution Technology Glossary

Where Quality Assurance aims to capture and describe the quality that any software delivered to EGI must meet, Quality Control ensures that the software will meet the quality described earlier.

Hence, Quality Control in EGI is involved in two phases of Quality Control in the relationships between EGI and its Technology Providers:

  • Proactive collaboration with Technology Providers relating to Test Plan execution and results.
  • Independent control of software quality covering key aspects of delivered software.

Controlling software quality is conducted in a two-step process. Both steps complement each other in the aspects of quality they control. Each step is described in greater detail below.


The contact person for Quality Assurance is Carlos Fernandez Sanchez,

Quality Criteria Verification

This first step of active Quality Control within EGI uses an independent reference testbed deployed at IBERGRID premises. Each Product delivered to EGI for quality control will be assessed based on the amount of changes, i.e.e bugs and/or security holes that have been fixed in the update, and the type and amount of new features, if any.

Quality Criteria Verification will focus on functional tests around the areas of change of the Product under verification.

For each Product that is tested in this step:

  • Each Verification officer records a detailed report of what has been verified, and the outcome of it.
  • An executive report summarises the verification efforts and the outcome (i.e. whether accepted or rejected). Guidance is given
    • to StageRollout which aspects of the Product to re-test or pay special attention to,
    • to DMSU for newly discovered, not fixed, or non-critical bugs with workarounds available, for future guidance and support to resource sites and users,
    • to Quality Assurance for reassessment of existing Quality Criteria, or to develop new Quality Criteria, if applicable.
    • to Technology Providers describing in which circumstances which component of the Product has developed the erroneous behaviour.

Each set of verification reports is permanently stored in EGI's document database and made publicly available for review.


Stage-Rollout complements the Quality Criteria Verification step in exposing the Product to real production conditions. Early Adopter sites that are interested in a timely rollout of the Product update take a part of their production infrastructure into a special "sandbox mode" where the Product update is installed under close scrutiny and exposed to a live environment and user requests.

The exact design and process of Staged-Rollout is described in the Operations context since [Staged-Rollout] needs close collaboration and planning within the Operations community.

Similar to Quality Criteria Verification, all Staged-Rollout activity is permanently stored in written reports per Product and will be publicly available for review and reference.