Shivvy,
1. In the Jan 24 meeting, the COSMOS
team decided that Linux is not in scope for COSMOS i8.
2. The 1/29/2008 build you refer
to may be deemed as the “first i9 build” and may be used to test
the Linux issues reported. As of this writing, we still need to determine
if all the Linux related defects will even be closed prior to this Jan 29 build.
3. Given the above two points,
Domenica’s question below still stands, i.e. “Does this conclude
your testing scope in i-8?”
4. We need to know this to
declare that i8 it closed and we can move on to i9. This is especially
critical given that i9 is a short iteration.
Thanks,
Jimmy Mohsin
Cell +1-609-635-1703
From: N, Shivashankari
Sent: Saturday, January 26, 2008 2:13 AM
To: Gjelaj, Domenica
Cc: Devine, John T; Stratton, Paul; Mohsin, Jimmy
Subject: RE: [cosmos-dev] Junit execution related issues
Domenica
QA has covered everything that was committed for i8. However COSMOS
may throw a Linux-friendly build on 29th Jan 08 (that’s what I
heard on 24th Jan 08 call) and QA should run the e2e on this build.
Regards
Shivashankari
Team Lead
India Technology Center
"If bugs were people then you would be China"
From: Gjelaj, Domenica
Sent: Saturday, 26 January 2008 12:16 AM
To: N, Shivashankari
Cc: Devine, John T; Stratton, Paul; Mohsin, Jimmy
Subject: RE: [cosmos-dev] Junit execution related issues
Shivy-
Does this conclude your testing scope in i-8?
-Domenica
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of N, Shivashankari
Sent: Friday, January 25, 2008 7:12 AM
To: Cosmos Dev
Subject: FW: [cosmos-dev] Junit execution related issues
We have executed below listed JUnit test suites and have attached
it’s test execution reports. Could someone
help us in moving them to cosmos CVS.
1) org.eclipse.cosmos/tests/org.eclipse.cosmos.dc.framework.test
(All passed)
-
Attached dcFrameworkTests_AllTests.zip file for test execution file
2) org.eclipse.cosmos.dc.cmdbf.services.tests
(All passed)
-
Attached dcCMDBfServiceTests_AllTests_1201243552613.zip file for
test execution file
3) org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.repository.tests
(Few failures)
-
Attached rmRepositoryTests_AllTests_1201255924953.zip file for test
execution file
4) org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.validation.tests
(Few failures)
-
Attached rmValidationTests_AllTests_1201256380351.zip file for test
execution file
Regards
Shivashankari
Team Lead
India Technology Center
"If bugs were people then you would be China"
From: Doma, Srinivas
Reddy
Sent: Friday, 25 January 2008 3:58 PM
To: N, Shivashankari
Subject: RE: [cosmos-dev] Junit execution related issues
Shivashankari,
Pl find Junit result files for below listed test suites and these
files have to be checked into CVS to generate Test pass reports:
5) org.eclipse.cosmos/tests/org.eclipse.cosmos.dc.framework.test
(All passed)
-
Attached dcFrameworkTests_AllTests.zip file for test execution file
6) org.eclipse.cosmos.dc.cmdbf.services.tests
(All passed)
-
Attached dcCMDBfServiceTests_AllTests_1201243552613.zip file for
test execution file
7) org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.repository.tests
(Few failures)
-
Attached rmRepositoryTests_AllTests_1201255924953.zip file for test
execution file
8) org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.validation.tests
(Few failures)
-
Attached rmValidationTests_AllTests_1201256380351.zip file for test
execution file
Thanks,
Srini
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On
Behalf Of David Whiteman
Sent: Friday, 25 January 2008 2:44 AM
To: Cosmos Dev
Cc: Hayes, Ian
Subject: Re: [cosmos-dev] Junit execution related issues
Since the
subject is "Here is the setup instructions for running junits for the
broker, domain, and data managers.", it's understandable if
"org.eclipse.cosmos.dc.cmdbf.services.tests" gets lumped in there,
since it's somewhat related to data managers. My question is why are
these two listed in Hubert's instructions, since they are not part of the
broker, domain, data manager trifecta:
org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.repository.tests
org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.validation.tests
David
"Ali
Mehregani" <ali.mehregani@xxxxxxxxx>
Sent by:
cosmos-dev-bounces@xxxxxxxxxxx
01/24/2008
03:29 PM
Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>
|
|
To
|
"Cosmos
Dev" <cosmos-dev@xxxxxxxxxxx>
|
cc
|
"Hayes,
Ian" <Ian.Hayes@xxxxxx>
|
Subject
|
Re:
[cosmos-dev] Junit execution related issues
|
|
org.eclipse.cosmos.dc.cmdbf.services.tests
is handled by the RM team. All tests of the project have already been
executed with 100% success.
Thanks,
Ali Mehregani
2008/1/24 N, Shivashankari <Shivashankari.N@xxxxxx>:
Hubert
Thank you.
There is one
more project required org.eclipse.cosmos.dc.cmdbf.services.tests (related to ER
212185)
There are 2
Junits (related to ERs 212187, 212189) outside these projects.
Regards
Shivashankari
Team Lead
India Technology Center
"If bugs were people then you would be China"
From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hubert
H Leung
Sent: Thursday, 24 January 2008 2:18 AM
To: Cosmos Dev
Cc: Hayes, Ian; cosmos-dev-bounces@xxxxxxxxxxx; Devine, John T;
Cosmos Dev
Subject: Re: [cosmos-dev] Junit execution related issues
Here is the setup instructions for running junits for the broker, domain, and
data managers. I added the instruction as a comment in the top level
junit (AllTests) as well.
1. Install TPTP 4.4.0.3 all-in-one package.
2. Install COSMOS SDK on top of the TPTP/eclipse install.
3. extract the following projects from CVS:
org.eclipse.cosmos/tests/org.eclipse.cosmos.dc.framework.test
org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.repository.tests
org.eclipse.cosmos/tests/org.eclipse.cosmos.rm.validation.tests
org.eclipse.cosmos/resource-modeling/org.eclipse.cosmos.rm.repository
org.eclipse.cosmos/resource-modeling/org.eclipse.cosmos.rm.validation
org.eclipse.cosmos/examples/org.eclipse.cosmos.samples.cmdbf.services
4. Start domain and broker and data managers:
Install the COSMOS Demo from the COSMOS donwload page. Install and
configure the demo application as documented at http://wiki.eclipse.org/COSMOS_DEMO_i8.
5. Start the Tomcat server on port 8080 (default)
6. Start data manager OSGi container. Use port 8081 (default).
7. Start the junit test (AllTests.testsuite)
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382
QA is facing issues while running the Junits (in Windows). We started with
the Data Collection part.
Steps
followed while testing them:
-------------------------------------------------
1.
Downloaded
eclipse and all other dependent libraries based on wiki page http://wiki.eclipse.org/COSMOSDataCollectorEnvironment#Download_Dependencies
2.
Checked
out all projects from cosmos/data-collection and resolved few compilation
issues and library dependencies
3.
Checked
out all tests from tests/data-Collection
4.
Bought
up tomcat running on port 8080
5.
Registered
broker with domain using COSMOS command line client
6.
Bought
up all Data Managers running outside eclipse (using
cosmos-demo\DataManagers\startup.bat)
7.
Finally,
executed JUnits one at time.
Issues
with:
-------------------
ManagementDomainTests.java
/ DataBrokerTests.java / ClientTests.java
-----------------------------------------------------------------------------------------------------------------
testManagementDomainClient
started...
org.apache.muse.ws.addressing.soap.SoapFault:
[ID = 'DestinationUnreachable'] There is no resource available at the given
EPR:
<wsa:EndpointReference
xmlns:wsa=" http://www.w3.org/2005/08/addressing">
<wsa:Address> http://domsr01-xp:8080/cosmos/services/org.eclipse.cosmos.dc.runtime.osgi.OSGiRuntimeHost
</wsa:Address>
<wsa:ReferenceParameters>
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing "
wsa:IsReferenceParameter="true"
xmlns:wsa="http://www.w3.org/2005/08/addressing
">RuntimeIdentifierValue</muse-wsa:ResourceId>
</wsa:ReferenceParameters>
</wsa:EndpointReference>
-----------
testDataBrokerClient
started...
org.apache.muse.ws.addressing.soap.SoapFault:
[ID = 'DestinationUnreachable'] There is no resource available at the given
EPR:
<wsa:EndpointReference
xmlns:wsa="
http://www.w3.org/2005/08/addressing">
<wsa:Address> http://domsr01-xp:8080/cosmos/services/org.eclipse.cosmos.dc.runtime.osgi.OSGiRuntimeHost</wsa:Address>
<wsa:ReferenceParameters>
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing "
wsa:IsReferenceParameter="true"
xmlns:wsa="http://www.w3.org/2005/08/addressing
">RuntimeIdentifierValue</muse-wsa:ResourceId>
</wsa:ReferenceParameters>
</wsa:EndpointReference>
org.apache.muse.ws.addressing.soap.SoapFault:
[ID = 'DestinationUnreachable'] There is no resource available at the given
EPR:
-------
<wsa:EndpointReference
xmlns:wsa="
http://www.w3.org/2005/08/addressing">
<wsa:Address> http://155.35.13.194:8080/cosmos/services/org.eclipse.cosmos.dc.local.registry.SQLProviderRegistry
</wsa:Address>
<wsa:ReferenceParameters>
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing "
wsa:IsReferenceParameter="true"
xmlns:wsa="http://www.w3.org/2005/08/addressing
">Resource_1</muse-wsa:ResourceId>
</wsa:ReferenceParameters>
</wsa:EndpointReference>
AssemblyTests/CollectionTests/QueryTests/SQLProviderRegistryTests
---------------------------------------------------------------------------------------------------------------
java.lang.RuntimeException : [ID =
'NoDataResource'] The resource 'muse.xml' does not exist or is not in the
classpath.
at org.apache.muse.core.AbstractEnvironment.getDataResourceStream(AbstractEnvironment.java:250 )
at org.apache.muse.core.AbstractEnvironment.getDocument(AbstractEnvironment.java:328 )
at org.apache.muse.core.platform.AbstractIsolationLayer.initialize( AbstractIsolationLayer.java:151)
at
org.eclipse.cosmos.dc.tests.runtime.SQLProviderRegistryTests.setUp(SQLProviderRegistryTests.java:65
)
at junit.framework.TestCase.runBare(TestCase.java:128 )
at junit.framework.TestResult$1.protect(TestResult.java:106 )
at junit.framework.TestResult.runProtected(TestResult.java:124 )
at junit.framework.TestResult.run(TestResult.java:109 )
at junit.framework.TestCase.run(TestCase.java:120 )
at junit.framework.TestSuite.runTest(TestSuite.java:230 )
at junit.framework.TestSuite.run(TestSuite.java:225 )
WSDMBindingTests.java/
WSDMBindingUtilTests.java /WSDMCustomCapabilityTests.java /
WSDMNotificationTests.java
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
java.lang.RuntimeException : [ID =
'NoDataResource'] The resource 'muse.xml' does not exist or is not in the
classpath.
at org.apache.muse.core.AbstractEnvironment.getDataResourceStream(AbstractEnvironment.java:250 )
at org.apache.muse.core.AbstractEnvironment.getDocument(AbstractEnvironment.java:328 )
at org.eclipse.cosmos.dc.tests.wsdm.binding.WSDMBindingTests.setUp(WSDMBindingTests.java:76 )
at junit.framework.TestCase.runBare(TestCase.java:128 )
at junit.framework.TestResult$1.protect(TestResult.java:106 )
at junit.framework.TestResult.runProtected(TestResult.java:124 )
at junit.framework.TestResult.run(TestResult.java:109 )
at junit.framework.TestCase.run(TestCase.java:120 )
at junit.framework.TestSuite.runTest(TestSuite.java:230 )
at junit.framework.TestSuite.run(TestSuite.java:225 )
QA requires
the http://wiki.eclipse.org/COSMOSDataCollectorEnvironment#Download_Dependencies
page
to be updated
so that our
Eclipse environment
is correct apart from the
approaches to run the
above JUnits.
Regards
Shivashankari
Team Lead
India
Technology Center
"If bugs were people then you would be China"_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
--
Ali Mehregani
COSMOS Project
http://www.eclipse.org/cosmos/
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev