This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 215135 - Establish a process for running JUnits against a COSMOS build
Summary: Establish a process for running JUnits against a COSMOS build
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P1 enhancement (vote)
Target Milestone: ---   Edit
Deadline: 2008-02-12
Assignee: Saurabh Dravid CLA
QA Contact: Hubert Leung CLA
URL:
Whiteboard:
Keywords:
Depends on: 211843 215078 222382 227191 233676 234771 234774 243400 247844
Blocks: 216591
  Show dependency tree
 
Reported: 2008-01-12 21:50 EST by Jimmy Mohsin CLA
Modified: 2012-01-03 13:47 EST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jimmy Mohsin CLA 2008-01-12 21:50:06 EST 
Assuming 211843 is resolved, which is supposed to fix Build issues, we need to establish a clear link between the Build and the JUnits.  Specifically, we need to clearly define how all the JUnits can be run against a build at machine located ANYWHERE....  We also need to clearly define both automated and manual parts of this effort.
Comment 1 Jimmy Mohsin CLA 2008-01-12 21:54:04 EST 
We need the ensure that the build process is platform independent.
Comment 2 Jimmy Mohsin CLA 2008-01-30 14:56:14 EST 
Please confirm that the build process will be completed wholly on COSMOS servers.
Comment 3 Ruth Lee CLA 2008-02-21 15:42:21 EST 
Changing these to i10 because we couldn't contain the work in i9. These are high priority for i10.
Comment 4 Bobby CLA 2008-04-15 09:46:00 EDT 
The test cases will be automated using the TPTP Automation Framework (ANT client).  Had issues with test case execution due to an error (org.eclipse.core.runtime.CoreException: IWAT4039E The Test Execution Harness reported the following problems:org.eclipse.hyades.internal.execution.local.control
.InactiveProcessException) in the internal RAC. See the bug report for details:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=222382

Found that as a workaround an external RAC can be started before running the automation framework. Proceeding with same, had issues with html report generation of test execution results. Current plan is to proceed with TPTP 4.4.1 as only 4.5 is having report generation issue.

A wiki has been created to capture test automation details and to determine the test cases that has to be automated and the required dependency and other test environment for the same. 
http://wiki.eclipse.org/COSMOS/COSMOS_TEST_AUTO
Comment 5 Bobby CLA 2008-05-30 03:35:56 EDT 
updating dependency bugs.....
Comment 6 Saurabh Dravid CLA 2008-09-24 10:45:38 EDT 
This bug is fixed as we have test automation infrastructure in place, but still some of the testsuites fails and give inconclusive results. Please refer the list of dependant bugs.