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 v1.1 I2 Test"
(→Testing Status of COSMOS Candidate Driver) |
|||
| Line 44: | Line 44: | ||
==== Testing status for ME ==== | ==== Testing status for ME ==== | ||
| + | org.eclipse.cosmos.me.btg.tests(tptp junit test) : 100% pass | ||
== Bugzilla status == | == Bugzilla status == | ||
Enter the status on the Iteration 2 Feature plan [http://wiki.eclipse.org/COSMOS_1.1_Iteration2_Features COSMOS v1.1 Iteration 2 Plan] | Enter the status on the Iteration 2 Feature plan [http://wiki.eclipse.org/COSMOS_1.1_Iteration2_Features COSMOS v1.1 Iteration 2 Plan] | ||
Revision as of 15:10, 11 February 2009
Contents
COSMOS v1.1 Iteration 2 Test pass
Testing Status of COSMOS Candidate Driver <>
Team, after you have updated your status on this page, send an email to Saurabh Dravid (sadravid at in.ibm.com) so that he can track when all of the status is posted and ready. To reduce noise on the mailing list, report to cosmos-dev only if you find a problem that other people need to know about and react to. Saurabh will post an email stating when the driver has passed all tests.
Data Collection and Visualization (Jimmy Mohsin)
For each of the following bullets, the team reporting testing status also confirms that the build reports are clean for their component(s):
- No usage of internal API outside of your own component, even within COSMOS
- No plug-ins or features are missing About.html or other legal information
- Copyright statements are present and correct in all files
- All strings have been externalized as the team developed
- All logging is consistent with COSMOS logging techniques
- All bugzillas that are complete have been closed
- All contributions from non-committers, if used, have been marked iplog+
Testing status for DC and DV
Resource Modelling (David Whiteman)
For each of the following bullets, the team reporting testing status also confirms that the build reports are clean for their component(s):
- No usage of internal API outside of your own component, even within COSMOS
- No plug-ins or features are missing About.html or other legal information
- Copyright statements are present and correct in all files
- All strings have been externalized as the team developed
- All logging is consistent with COSMOS logging techniques
- All bugzillas that are complete have been closed
- All contributions from non-committers, if used, have been marked iplog+
Testing status for RM
Management Enablement (Jason Losh)
For each of the following bullets, the team reporting testing status also confirms that the build reports are clean for their component(s):
- No usage of internal API outside of your own component, even within COSMOS
- No plug-ins or features are missing About.html or other legal information
- Copyright statements are present and correct in all files
- All strings have been externalized as the team developed
- All logging is consistent with COSMOS logging techniques
- All bugzillas that are complete have been closed
- All contributions from non-committers, if used, have been marked iplog+
Testing status for ME
org.eclipse.cosmos.me.btg.tests(tptp junit test) : 100% pass
Bugzilla status
Enter the status on the Iteration 2 Feature plan COSMOS v1.1 Iteration 2 Plan