COSMOS/COSMOS TEST AUTO

1) Introduction

This page provides information and links related to Test Automation of COSMOS junits.

2) Test Automation Overview

The COSMOS build is based on Eclipse PDE (Plug-in Development Environment) and it runs in the eclipse server. Currently the candidate drivers at the end of an iteration are manually tested by the respective component teams. This initiative is to define the process of testing and automate junit execution as part of the build. By automating and integrating with the build, testing can be done more often and bugs will be discovered early on.

The test cases are available in CVS at the following location:


Go to HEAD -> org.eclipse.cosmos -> tests

3) Test Details

The following table briefly explains the different contacts for the test cases as well as the pre reqs and test setup needed to execute it.

Sl No	Component	Test Project	Contact Person	Dependencies	Test Setup	Test Automation
1	data-collection	org.eclipse.cosmos.dc.cmdf.services.tests	David Whiteman	org.eclipse.cosmos.common.tests	The directory in testTempDirectory in CMDBfTestMessages.properties will be created. This will need to be changed from the default for Linux testing.	Done, AllTests.testsuite works
2	data-collection	org.eclipse.cosmos.dc.framework.test	?	?	?
3	data-collection	org.eclipse.cosmos.dc.stat.datamgr.testing	?	?	?
4	data-collection	org.eclipse.cosmos.dc.tests	?	?	?
5	data-collection	org.eclipse.cosmos.example.mdr.registration.tests	Ali Mehregani	COSMOS environment	This test requires the COSMOS environment to be running before the test is executed. It's meant to perform functional testing on the registration service. It's probably unrealistic to run this plug-in against each build. I would exclude this test from your test automation framework
1	data-reporting	org.eclipse.cosmos.dr.tests	Sheldon Lee-Loy		Can not be automated. This project contains manual tests.
2	data-reporting	org.eclipse.cosmos.dr.tests.drs.service.handler	Sheldon Lee-Loy		The COSMOS End 2 End should be deployed on http://localhost:8080
3	data-reporting	org.eclipse.cosmos.dr.tests.drs.service.handler.tptp	Sheldon Lee-Loy	org.eclipse.cosmos.dr.tests.drs.service.handler	The COSMOS End 2 End should be deployed on http://localhost:8080
4	data-reporting	org.eclipse.cosmos.dr.tests.views	Sheldon Lee-Loy		Can not be automated. This project contains manual tests.
5	data-reporting	org.eclipse.cosmos.dr.tests.web.ui	Sheldon Lee-Loy		Can not be automated. This project contains manual tests.
1	management-enablement	org.eclipse.cosmos.me.dmtoolkit.tests	David Whiteman	org.eclipse.cosmos.common.tests, Webtools platform	One manual test in addition to a plugin test.
2	management-enablement	org.eclipse.cosmos.me.management.tests	?	?	?
1	resource-modeling	org.eclipse.cosmos.rm.repository.tests	David Whiteman	org.eclipse.cosmos.common.tests	See org.eclipse.cosmos.rm.repository.tests/src/org/eclipse/cosmos/rm/repository/tests/common/testMessages.properties and org.eclipse.cosmos.rm.repository.tests/src/META-INF
2	resource-modeling	org.eclipse.cosmos.rm.smlif.tests	David Whiteman	org.eclipse.cosmos.common.tests	Configure artifacts in org.eclipse.cosmos.rm.smlif.tests/test-resources. Open the TPTP artifacts to see documentation on what is required.
3	resource-modeling	org.eclipse.cosmos.rm.validation.tests	David Whiteman	org.eclipse.cosmos.common.tests	See org.eclipse.cosmos.rm.validation.tests/src/org/eclipse/cosmos/rm/validation/internal/common/testMessages.properties. Also need to configure artifacts in org.eclipse.cosmos.rm.validation.tests/test-resources for plugin tests (open the artifacts to read documentation on doing this).

We will try to automate as much as possible from the above list using the TPTP Test Automation Framework.