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.
Talk:COSMOS Design 214576
Revision as of 07:01, 11 January 2008 by Unnamed Poltroon (Talk)
--Popescu.ca.ibm.com 09:36, 8 January 2008 (EST)
- Assess localization support; validate that the code can run on non-english locales.
- This type of testing will not happen on every iteration, most likely not even on every release. This is a placeholder to keep track of translatability testing once COSMOS offers localization support.
Tmakins.us.ibm.com 16:33, 10 January 2008 (EST)
- We should clarify which activities will be executed for each iteration and which will only be executed for milestones.
- General Question: I assume that specifics on test cases, platforms, metrics, etc. will be documented in a QA plan which will be based on this document?
Paul Stratton. CA. 11-jan-2008
UNIT testing - what framework will be used to run the JUNIT tests - Eclipse ? Will QA perfrom regression testing using JUNITS from previous iterations ? Will manual tests be run within TPTP ? Are there any plans for QA to supplement current UNIT tests where they are considered inadequate ?
End to End Testing - What is the strategy to automate this testing and provide a more comprehensive coverage ?