Skip to main content
Jump to: navigation, search

Difference between revisions of "COSMOS QA i10 Activities"

('''In scope platforms, OS's & configurations''')
('''In scope platforms, OS's & configurations''')
Line 57: Line 57:
# Internet Explorer (6.0.2900.2180.XP SP2)
# Internet Explorer (6.0.2900.2180.XP SP2)
# Eclipse 3.4
# Eclipse 3.4
# DOJO 1.0.2
== '''Iteration QA Entrance and Exit Criteria''' ==
== '''Iteration QA Entrance and Exit Criteria''' ==

Revision as of 02:15, 11 April 2008

COSMOS QA Activities for i10

This has been put together to address Bugzilla ER 222932.


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/behavioural 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 i10 testing:

Primary Tasks:

  1. E2E testing on Windows XP, 2003 and Red Hat Enterprise Linux Server 5.0


  1. i10 ERs – JUnits/Manual Tests inspection (
  2. Data Visualization TPTP Manual Tests Execution (DataVisualization.UI.Component.Widget.testsuite / UI.Reports.testsuite)

Secondary Tasks:

  1. Execution of i10 supplement e2e tests(negative) from QA.
  2. Basic operational efficiency tests (limited performance tests)

In scope i10 ERs

Please refer to for the list of ERs that QA will need to test as part of the i10 testing phase that runs from April 21 thru 2nd May 2008.

In scope platforms, OS's & configurations

Align with Ganymede:

For i10, 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 i10, 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. DOJO 1.0.2

Iteration QA Entrance and Exit Criteria

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

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

The following items need to be in place before the 2 week i10 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 i10, 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 i10 ( are run against the final i10 build

i10 Test Cases

QA will add End2End i10 test cases and will provide the link over here.

Resources & timeframe

i10 QA will be completed by two dedicated CA resources. The i10 QA phase will run from April 21 thru May 2.

Task Breakdown

This section includes the tasks required to complete this enhancement.

  1. Srinivas Reddy has generated this page to address bugzilla 222932
  2. The COSMOS team needs to review the relevant sections for this page.
  3. Kishore Adivishnu/Srinivas, representing the QA team, is supposed to complete this activity by April 18, 2008. This is prior to the commencement of the QA phase for i10.

Open Issues/Questions

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

Back to the top