Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS QA i9 Activities"
(→'''Is COSMOS 1.0 well-formed software?''') |
(→'''Operational Efficiency considerations''') |
||
| Line 75: | Line 75: | ||
|} | |} | ||
| − | == ''' | + | == '''TBD''' == |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== '''Task Breakdown''' == | == '''Task Breakdown''' == | ||
Revision as of 20:48, 24 January 2008
Contents
COSMOS QA Activities for i9
This has been put together to address Bugzilla ER 216529.
Terminologies/Acronyms
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. |
Purpose
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.
Since i9 is the first iteration to utilize the QA Expectations, we need to define the i9 QA activities upfront. This will enable us to translate the QA Expectations into an actionable series of steps that ensure QA coverage for i9. This will also serve as the QA plan for i9. Depending on how we execute the QA cycle this time around, we may append to the COSMOS Development Process.
Is COSMOS 1.0 a consumable entity?
COSMOS QA perceives COSMOS 1.0 as a consumable (adoptable) software if we can demonstrate its capability to successfully integrate with participating data managers and MDRs through integration and performance testing reports, code samples and other adopter aids.
Clear documentation, process definition for fixing COSMOS bugs or supporting future COSMOS enhancements and a plan for scaling COSMOS as dependent software upgrade themselves can also contribute.
| Quality Expectation | Acceptance Criteria | QA Role |
|---|---|---|
| Successful integration of COSMOS components | COSMOS team must provide helper applications for integration testing with scenarios 208274 (i9) 209990 (future) | Perform integration testing and execute scenarios – manual. Recorded as manual TPTP tests |
| COSMOS stability during production deployments | COSMOS team must state the minimum system requirements for production. Also recommend parameters (number of data Managers / MDRs that may be added, volume of data that can be queried, etc.) that should be considered for these tests. | Execute performance / scalability /volume/stress/ availability testing with minimum resources recommended |
| COSMOS support across products / data sources | COSMOS team must state the kinds of MDRs that can be integrated and provide samples 211093 (future) 214766 (i8) 209987 (i9) 201302 (i8) 201317 (i8) 212187 (i8) 212189 (i8) | Execute integration tests with these samples – manual. Recorded as TPTP manual tests |
| User documentation | COSMOS team will write manuals 214805 (i9) | QA validates the information - manual |
| Samples / skeleton MDR implementation / any collateral | COSMOS team must provide samples 208274 (i9) 202332 (no target) 200567 (i8) | QA validates the existence and may require assistance from COSMOS Team while using the skeleton implementations – manual. Recorded as TPTP manual tests |
| Additional platforms | COSMOS team must specify | QA will certify the product on these platforms - manual |
| Dependencies on other open source software | COSMOS team to define a process to integrate with the newer versions of these dependent software 215609 (no target) | QA will validate the process - manual |
| Future enhancements / bug reporting mechanism | COSMOS team to set a process Bugzilla | QA validates the process - manual |
TBD
Task Breakdown
This section includes the tasks required to complete this enhancement.
- Jimmy Mohsin has generated this page to address bugzilla 216529
- The COSMOS team needs to identify the relevant section for this page.
- Shivvy, representing the QA team, is supposed to complete this activity by Februrary 22, 2008. This is prior to the commencement of the QA phase for i9.
Open Issues/Questions
All reviewer feedback should go in the Talk page for 216529.