Skip to main content
Jump to: navigation, search

COSMOS QA i14 Activities

COSMOS QA Activities for i14

This has been put together to address bugzilla 249571.

For all these activities, test execution has been tracked over


The terminologies/acronyms below are commonly used throughout this document. The list below defines each term regarding how it is used in this document.

Term Definition
Quality Expectations Is a statement of some behaviour, characteristic or operational facility that a product must exhibit for it to be deemed ‘fit for purpose’. Quality expectations are normally grouped into four main categories: functional/behavioural, operational efficiency, inter operability factors; and admin/management factors (to control TCO).
Acceptance Criteria This is a quantification of how a quality expectation is to be validated. For functional/behavioral quality expectations this is a simple Boolean test – it either works or it doesn’t. Hence, for most scope docs there is no need to specifically define functional acceptance criteria. However, other types of quality expectations – especially performance related areas – do require specific acceptance criteria because the quantification is normally some form of numeric threshold (with optional margin/tolerance) that states minimum levels of acceptable operational efficiency.

Scope Definition

The COSMOS quality expectations and the matching acceptance criteria, that would serve as a preamble to the COSMOS QA team while executing their work, were completed via ER 214576.

QA Scope for i14 testing:

Primary Tasks:

  1. E2E testing on Windows XP, 2003 and Red Hat Enterprise Linux Server 5.0 (
  2. Data Visualization TPTP Manual Tests Execution (DataVisualization.UI.Component.Widget.testsuite / UI.Reports.testsuite)
  3. Execution of i14 supplement e2e tests(negative) from QA.
  4. MDR Toolkit and SML Tooling tests
  5. Basic operational efficiency tests (limited performance tests)

In scope platforms, OS's & configurations

For i14, QA will certify the following platforms:

  1. Microsoft Windows XP SP2
  2. Micorsoft Windows 2003 Server SP1
  3. RedHat Linux Enterprise Server 5.0 (Smoke test/Limited End2End testing only)

For i14, QA will use following softwares:

  1. Tomcat 5.5.25 & Axis2 1.3
  2. SUN JDK 1.5.0_15
  3. Firefox version (
  4. Internet Explorer (6.0.2900.2180.XP SP2)
  5. Eclipse 3.4
  6. BIRT 2.3

Iteration QA Entrance and Exit Criteria

The following items need to be in place before the 2 weeks i14 QA phase can commence:

  1. A stable i14 build that has undergone multiple integration build during the course of the Development phase which ends on Oct 25, 2008
  2. The wiki page is completed (by Development)

The following items need to be in place before the 2 week i14 QA phase can be declared complete:

  1. All ERs should have JUnits or a manual TPTP test in place. If JUnits are not applicable to a given ER, alternative verification means need to be specified. To reiterate, QA is not expected to run the JUnits. In i14, this activity will be completed as part of the weekly iteration builds. In future, this will be fully automated once ER 215135 is completed.
  2. The e2e tests for i14 ( are run against the final i14 build

i14 Test Cases

All End2End tests from QA can be found here -

Resources & timeframe

i14 QA will be completed by two dedicated CA resources. The i14 QA phase will run from 27th Oct'08 to 14th Nov'08 (3 weeks).

Task Breakdown

This section includes the tasks required to complete this enhancement.

  1. Srinivas Reddy has generated this page to address bugzilla 249571
  2. Srinivas, representing the QA team, is supposed to complete this activity by Oct 24, 2008. This is prior to the commencement of the QA phase for i14.

Open Issues/Questions

All reviewer feedback should go in the Talk page for 238087 "Define scope and detail the i14 QA activities".

Back to the top