Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

CosmosDataReportingComponent10 Testing Guide

Back to Data Reporting Design


This document provides the UI infrastructure code based on 209226 UI Visualization infrastructure design document.

The reader should be aware that the modules for the User Interface follow a team sharing structure. The team structure strategies outlined in "Eclipse Web Tools Platform: Developing Java Web Applications" technical document were used. Chapter 6 covers these stategies: Organize your Web Tools platform (WTP) development project.

One can view chapter 6 online at




  • You now need to define a Tomcat Server Runtime. Go to Windows>Preferences..
  • Select the "Server>Installed Runtimes" node and click the "Add.." button.


  • Specify Apache Tomcat 5.5 runtime and click Next.


  • Enter the location of the tomcat directory and click Finish. Then click OK.


  • Now you need to set up the org.eclipse.cosmos.examples.e2e.web.ui directory. Note that the WebContent directories under the org.eclipse.cosmos.examples.e2e.web.ui use linked folders. This step is needed since eclipse does not use relative paths to link folders.
    • Right click the org.eclipse.cosmos.examples.e2e.web.ui project and create a new Folder by selecting New>Folder from the popup menu. Click the "<<Advance Button" and click the "Link to folder in the file system" check box


    • Click the "Variables..." button. This should bring up a dialog box.
    • Then click the "New..." button. This should bring up dialog box where you can enter a variable name. The linked folders use a variable named "WORKSPACE" to resolve the workspace directory. Therefore we need to define this variable as follows:


    • Click OK, Click OK again and then Cancel. Note that we don't want to create a directory we just needed to add a variable name since the directories are already created.
  • Right click the org.eclipse.cosmos.examples.e2e.web.ui project and select "Refresh".
  • Right click the org.eclipse.cosmos.dr.tests.web.ui and select "Refresh".
  • At this point the workspace is setup to run. Right click the org.eclipse.cosmos.examples.e2e.web.ui project and select "Run As>Run on Server".
  • Select Tomcat v5.5 Server and click Next


  • Make sure that org.eclipse.cosmos.dr.tests.web.ui and org.eclipse.cosmos.examples.e2e.web.ui projects are selected and click Finish. The server will start.


Running UI Test Page

  • Now open FireFox 2.0 or IE 6+ and type http://localhost:8080/COSMOSUITests/?page=tests. You should see the COSMOS UI Test Page. This page provides several configured test pages that tests widgest and various data visualization components.


  • The following shows the test page to test the COSMOS tree widget. As you can see that the page presents three configuration of the tree. The tester would normally view this page and make sure that the widget is rendered and operates properly.



Creating Outputter Testcases

  • It is very easy to create unit tests cases for an outputter. First be aware that an outputter tests is basically sending an input request to the outputter and recieving a output stream. A basic test would be compose of sending an input to an outputter and comparing the output produced with an expected output. The COSMOS UI Outputter Test requires the following files:
    • An input file that contains the parameters for the outputter
    • An output file that contains the expected generated output based on the input parameters
  • The following diagram shows where to deploy the input and output file in the COSMOS UI test environtment:


  • Note that the directory of the input and output file indicates the outputter id to test against. For example, saving a input and output file under tests\handler\org\eclipse\cosmos\examples\dr\drs\service\outputter\CBEDataManager\ indicates that the test harness should make the following url request:
  • The following shows a sample input file:
  • Note that the input file is similar to a properties file that has name value pairs. The about input file indicates an input parameter with a value of 'getAllMDRs'. These parameters will be sent when a request is made to the outputter.
  • The following is a sample output file:
{ identifier: "object",  label: "title",  items:[{nodeClass:"mdrstat",expandQuery:"statQuery",title:"Statistical Data",object:"119499171",epr:"", store:"[{name:'EPR', properties:[{name:'EPR', value:''},{name:'classification', value:'statistical'}]}]"},{nodeClass:"mdrcbe",title:"Monitoring Data",object:"119458269916711",epr:"", expandQuery:"cbeQuery",store:"[{name:'EPR', value:''},{name:'classification', value:'cbef'}]"},{nodeClass:"mdr",title:"Asset Repository",object:"0",epr:"http://cantata:8081/cosmos/services/org.eclipse.cosmos.rm.dataManager.sml.impl.SmlRepositoryDataManager", store:"[{name:'EPR', value:'http://cantata:8081/cosmos/services/org.eclipse.cosmos.rm.dataManager.sml.impl.SmlRepositoryDataManager'},{name:'muse-wsa:ResourceId', value:'Asset Repository'}]"}]}
  • Note the above content shows the json structure that will be produced by the outtputer. The test will compare the above content with the response it gets back from the outputter. If the content and the response matches the test is successful otherwise the test fails.

Testing COSMOS Reports

COSMOS Reporting System is a separate component from the COSMOS UI. This system can be tested independantly from the UI. The following illustrates the architecture of the reporting system.


A report test consists of sending report parameters to a report and making sure the report is rendered correctly. Currently the report tests consists of links to the reporting system that will render the Log report and Statistical report. These links are as follows:

Note that these links point to configuration pages that the user can use to specify the report parameters. The user can use the default parameters and render the report.

Back to the top