Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOS QA Criteria"
Jim.gyng.com (Talk | contribs) (→'''Change History''') |
Jim.gyng.com (Talk | contribs) (→'''Purpose''') |
||
| Line 53: | Line 53: | ||
== '''Purpose''' == | == '''Purpose''' == | ||
The QA Creiteria will be specified by the COSMOS team; and will be used to specifiy the exit for all COSMOS 1.0 iterations going forward. The intent is to apply these criteria to i9 onwards. | The QA Creiteria will be specified by the COSMOS team; and will be used to specifiy the exit for all COSMOS 1.0 iterations going forward. The intent is to apply these criteria to i9 onwards. | ||
| + | |||
<p> | <p> | ||
| − | The | + | The QA team will use these criteria as a master guide to define and plan all their testing efforts. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
</p> | </p> | ||
Revision as of 02:47, 8 January 2008
Contents
- 1 COSMOS QA Creiteria
- 2 Workload Estimation
- 3 Terminologies/Acronyms
- 4 Purpose
- 5 Is COSMOS 1.0 well-formed software?
- 6 Identify all the end-to-end tests
- 7 Is COSMOS 1.0 a consumable entity?
- 8 Is COSMOS 1.0 an extensible framework?
- 9 Does COSMOS 1.0 offer good features & reference implementations?
- 10 Task Breakdown
- 11 Open Issues/Questions
COSMOS QA Creiteria
Change History
| Name: | Date: | Revised Sections: |
|---|---|---|
| Jimmy Mohsin | 01/3/2008 |
|
Workload Estimation
| Process | Sizing | Names of people doing the work |
|---|---|---|
| Initial specification | 2 | Jimmy Mohsin |
| Review by COSMOS team | 2 | COSMOS Team |
| Review and sign-off | 1 | QA Team |
| TOTAL | 5 |
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 (Shivvy, please fill in this section)
| Term | Definition |
|---|---|
| TBD | Shivvy will fill in this section. |
Purpose
The QA Creiteria will be specified by the COSMOS team; and will be used to specifiy the exit for all COSMOS 1.0 iterations going forward. The intent is to apply these criteria to i9 onwards.
The QA team will use these criteria as a master guide to define and plan all their testing efforts.
Is COSMOS 1.0 well-formed software?
The COSMOS code must consider the following guidelines to support i18n:
- Assess the JUnits as well as any other type of tests
- Evaluate the integration tests
- Evaluate the iteration and milestone close processes
- Assess the open source tooling used to test COSMOS 1.0
- Review the RE process
Identify all the end-to-end tests
All COSMOS 1.0 iterations must pass the following end-to-end tests:
- Scalability
- We need to specifiy details of this capability
- Performance
- We need to specifiy details of this capability
- Concurrency
- We need to specifiy details of this capability
- Availability
- We need to specifiy details of this capability
- Stress testing
- We need to specifiy details of this capability
Is COSMOS 1.0 a consumable entity?
In order to ensure ease of adoption for COSMOS 1.0, the following items need to be addressed:
- Asses install documentation, i.e. is there enough information on the download page to be able to install the required functions ?
- Asses Update Manager capabilities (not there yet…)
- Are the offered packages fully functional, i.e. the content described on the install page matches the downloaded package
- Assess case for COSMOS 1.0 to Executive Management
- Assess package for adopting developers
- Asses package for other types of adopters, if applicable
- Evaluate hardware & software prerequisite definition
- Evaluate upgrade and patch process for COSMOS 1.0
Is COSMOS 1.0 an extensible framework?
In order to ensure that COSMOS 1.0 can be extended as desired by the adopters, the following items need to be addressed:
- Asses user documentation and API doc
- Assess process for extending framework components
- Assess process for extending supported platforms / operating systems
- Review process for reporting bugs and ehnancement requests
Does COSMOS 1.0 offer good features & reference implementations?
- Is it easy to deploy the central infrastructure, i.e. the Broker / Domain / et al?
- How hard is it to plug in an MDR into an existing COSMOS 1.0 framework?
- What Data Managers / MDR types are supported out of the box?
Task Breakdown
The following section includes the tasks required to complete this enhancement.
- Jimmy Mohsin has generated this page
Open Issues/Questions
All reviewer feedback should go in the Talk page for 214576.
- Should there be additional criteria for Milestones?