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 Criteria"
(→'''Is COSMOS 1.0 well-formed software?''') |
(→'''Message Handling Considerations''') |
||
| Line 103: | Line 103: | ||
## We need to specifiy details of this capability | ## We need to specifiy details of this capability | ||
| − | == ''' | + | == '''Ensure COSMOS 1.0 is a consumable entity''' == |
| − | + | To ease the adoption of COSMOS 1.0, the following | |
| − | # | + | # 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 prerequisite definition | ||
| + | # Evaluate upgrade and patch process for COSMOS 1.0 | ||
== '''i18n Checklist''' == | == '''i18n Checklist''' == | ||
Revision as of 02:17, 8 January 2008
Contents
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:
| Term | Definition |
|---|---|
| Internationalization | The process of generalizing the design of a product so that it can handle multiple languages and cultural conventions without the need for making code changes for each language. COSMOS 1.0 will be internationalized for its eventual adoption and deployment |
| Localization | The process of taking an internationalized product and making it linguistically and culturally appropriate to the target locale (country/region and language) where it will be used. COSMOS 1.0 will not be localized for any non-US English languages, this is something that the adopers will need to do. |
| Translatable Elements | Everything intended to be locale and language dependent. These items may need to be modified for different locales, e.g. date formats, time formats, word lists for content controls, and so on. |
| Non-user elements | Everything not intended for end-users to see and understand. This fits into two categories, proper names and internal elements. Examples of internal elements are command line commands and options, debug strings, registry keys, program file names, comments, and so on. Examples of proper names are product name, company name, and so on. |
| User Elements | Everything intended for end-users to see and understand, e.g. menus and menu items, dialog boxes, windows, program groups, error messages, installation scripts, icons, buttons, "Display Name" and "Description" fields for services we create on Windows, and so on. |
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 data visualization component does not follow a consisten design pattern to support internationalization. There are serveral components within the visualization project that require internationalization support:
- Dojo widgets
- Servlet data feeds
- XML configuration files
- ANY OTHER COMPONENTS ???
Ensuring COSMOS 1.0 is 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
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
Ensure COSMOS 1.0 is a consumable entity
To ease the adoption of COSMOS 1.0, the following
- 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 prerequisite definition
- Evaluate upgrade and patch process for COSMOS 1.0
i18n Checklist
Here is a check list to determine whether COSMOS is i18n-ready or not:
- Menus, dialogs and web layouts can tolerate text expansion
- Development language strings are reviewed for meaning and spelling to reduce user confusion and lessen translation errors
- Third-party software used in the product is examined for i18n support
- Consistent terminology is used in messages
- COSMOS runs properly in its base language in all target locales
- Strings are not assembled by concatenation of fragments
- Source code does not contain hard-coded character constants, numeric constants, screen positions, filenames or pathnames that assume a particular language
- String buffers are large enough to handle translated words and phrases
- East Asian editions support line-breaking rules
- All international editions of the program are compiled from one set of source files
- Localizable items are stored in resource files, message tables or message catalogues
- All language editions share a common file format
- Program handles non-homogeneous network environments where machines are operating with different encodings
- No assumptions are made that one character storage element represents one linguistic character
- Code does not use embedded font names or make assumptions about particular fonts being available
- Program displays and prints text using appropriate fonts
- Sorting and case conversion are culturally correct
- Application works correctly on localized editions of the target operating system(s)
- Specific for web internationalization:
- Check middle-tier components for internationalization compliance
- Ensure that information about encoding and locale of data is passed correctly between presentation and backend tiers
Task Breakdown
The following section includes the tasks required to complete this enhancement.
- TBD
Open Issues/Questions
All reviewer feedback should go in the Talk page for 208593.
- Should this ER address the Language Groups issue? Or should this be deemed out of scope since COSMOS 1.0 will not address localization?
- Where does XLIFF fit into the i18n considerations? http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core.html
--Popescu.ca.ibm.com 13:23, 4 January 2008 (EST)XLIFF is one option for localization support in xml documents.