Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "COSMOS v1.1 I2 Test"

(Testing Status of COSMOS Candidate Driver)
 
(4 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
* [http://www.eclipse.org/cosmos/downloads/?buildId=COSMOS-1.1.0-200902091100 Driver download]
 
* [http://www.eclipse.org/cosmos/downloads/?buildId=COSMOS-1.1.0-200902091100 Driver download]
 
* [http://www.eclipse.org/cosmos/downloads/?reports=COSMOS-1.1.0-200902091100 Build reports]
 
* [http://www.eclipse.org/cosmos/downloads/?reports=COSMOS-1.1.0-200902091100 Build reports]
 +
* [http://www.eclipse.org/cosmos/test/reports/1.1.0_i2/ Test pass reports]
  
  
Line 30: Line 31:
 
* All bugzillas that are complete have been closed
 
* All bugzillas that are complete have been closed
 
* All contributions from non-committers, if used, have been marked iplog+
 
* All contributions from non-committers, if used, have been marked iplog+
 +
 +
<font color=red>All the above are confirmed. - DLW</font>
  
 
==== Testing status for RM ====
 
==== Testing status for RM ====
 +
 +
<font color=red>No stop ship problems to report. - DLW</font>
 +
 +
* [http://www.eclipse.org/cosmos/test/reports/1.1.0_i2/junit/org.eclipse.cosmos.rm.repository.tests/index.html org.eclipse.cosmos.rm.repository.tests]
 +
* [http://www.eclipse.org/cosmos/test/reports/1.1.0_i2/junit/org.eclipse.cosmos.rm.smlif.tests/index.html org.eclipse.cosmos.rm.smlif.tests]
 +
* [http://www.eclipse.org/cosmos/test/reports/1.1.0_i2/junit/org.eclipse.cosmos.rm.validation.tests/index.html org.eclipse.cosmos.rm.validation.tests]
  
 
=== Management Enablement (Jason Losh) ===
 
=== Management Enablement (Jason Losh) ===
Line 42: Line 51:
 
* All bugzillas that are complete have been closed
 
* All bugzillas that are complete have been closed
 
* All contributions from non-committers, if used, have been marked iplog+
 
* All contributions from non-committers, if used, have been marked iplog+
 +
 +
<font color=red>All the above are confirmed. - WJL</font>
  
 
==== Testing status for ME ====
 
==== Testing status for ME ====
org.eclipse.cosmos.me.btg.tests(tptp junit test) : 100% pass  
+
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]

Latest revision as of 01:48, 26 February 2009

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+

All the above are confirmed. - DLW

Testing status for RM

No stop ship problems to report. - DLW

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+

All the above are confirmed. - WJL

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

Back to the top