Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

COSMOS QA End2End Tests

Revision as of 01:00, 27 May 2008 by Unnamed Poltroon (Talk) (→‎Using the COSMOS Web User Interface)

Overview

The purpose of this page is to articulate all COSMOS End-to-End test scenarios for QA testing. This page will be filled in by the QA team and will be updated with every new iteration.

COSMOS Installation

As a pre-requisite for below test scenarios, install the COSMOS application as per the instructions available at http://wiki.eclipse.org/COSMOS_DEMO_i11#Installation

COSMOS End2End Tests

Build Installation and Configuration

Test Description:

  • To test Build installation with default configuration
  1. configDemo.bat C:\cosmos\i11\apache-tomcat-5.5.25 C:\cosmos\i11\cosmos-demo C:\cosmos\i11\birt-runtime-2.3M6.zip C:\cosmos\i11\dojo-release-1.0.2.zip C:\cosmos\i11\axis2.war

Expected Result:

  • Unzipping C:\cosmos\i11\axis2.war to C:\cosmos\i11\apache-tomcat-5.5.25\webapps\axis2...
  • Installed axis2 on Apache Tomcat server.
  • Installed web application: COSMOSReportViewer
  • Installed web application: COSMOSUI
  • Unzipping C:\cosmos\i11\birt-runtime-2.3M6.zip to C:\cosmos\i11\apache-tomcat-5.5.25\webapps/COSMOSReportViewer...
  • Unzipped BIRT to COSMOSReportViewer
  • Copied BIRT web viewer example to COSMOSReportViewer
  • Unzipping C:\cosmos\i11\dojo-release-1.0.2.zip to C:\cosmos\i11\apache-tomcat-5.5.25\webapps/COSMOSUI...
  • Unzipped dojo to COSMOSUI.
  • Installed web service: AperiMdr
  • Installed web service: Broker
  • Installed web service: ExampleMdr
  • Installed web service: LoggingDataManager
  • Installed web service: ServiceFinder
  • Installed web service: SMLMDR
  • Installed web service: StatDataManager
  • Installed web service: TestFederatingCMDB
  • Copied axis jar files to COSMOSUI.
  • Copied axis jar files to COSMOSReportViewer.
  • Copied axis jar files to cosmos client.
  • Updated axis2.xml.
  • Updated services.xml for SML MDR.
  • Updated services.xml for statistical MDR.

Starting COSMOS components : Management Console

Test Description:

  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:8080/axis2/services/Broker

Expected Result:

Test Description:

  1. COSMOS> broker registerAllDataManagers

Expected Result:

  • log4j:WARN No appenders could be found for logger (org.apache.axis2.util.Loader).
  • log4j:WARN Please initialize the log4j system properly.
  • Registering StatDataManager
  • Registering LoggingDataManager
  • Registering TestFederatingCMDB
  • Registering ExampleMdr
  • Registering SMLMDR
  • Registering AperiMdr
  • DataManagers registered

Test Description:

  1. COSMOS> broker getDataManagers

Expected Result:

Test Description:

  1. COSMOS> finddatamanagers http://localhost:8080/axis2/services/CosmosServiceFinder

Expected Result:

Test Description:

  1. COSMOS> broker deregister domsr01-xp StatDataManager

Expected Result:

  • DataManager deregistered.

Test Description:

  1. COSMOS> broker deregister domsr01-xp LoggingDataManager

Expected Result:

  • DataManager deregistered.

Test Description:

  1. COSMOS> broker deregister domsr01-xp TestFederatingCMDB

Expected Result:

  • DataManager deregistered.

Test Description:

  1. COSMOS> broker deregister domsr01-xp ExampleMdr

Expected Result:

  • DataManager deregistered.

Test Description:

  1. COSMOS> broker deregister domsr01-xp SMLMDR

Expected Result:

  • DataManager deregistered.

Test Description:

  1. COSMOS> broker deregister domsr01-xp AperiMdr

Expected Result:

  • DataManager deregistered.

Test Description:

  1. COSMOS> graphQuery domsr01-xp SMLMDR D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\SMLMDR\testInstanceIdQuery.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp SMLMDR D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\SMLMDR\testPropertyQuery.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp ExampleMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\ExampleMDR\all-students.txt

Expected Result:

  • GraphQuery response:
  • <?xml version="1.0" encoding="UTF-8"?><cmdbf:queryResult xmlns:cmdbf="http://cmdbf.org/schema/1-0-0/datamodel">
  • <cmdbf:nodes templateId="items">
  • <cmdbf:item>
  • <cmdbf:record xmlns="http://school">
  • <student>
  • <identity firstName="Mike" id="03" lastName="Lee"/>
  • </student>
  • <cmdbf:recordMetadata>
  • <cmdbf:recordId>03</cmdbf:recordId>
  • </cmdbf:recordMetadata>
  • </cmdbf:record>
  • <cmdbf:instanceId>
  • <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId>
  • <cmdbf:localId>03</cmdbf:localId>
  • </cmdbf:instanceId>
  • </cmdbf:item>
  • <cmdbf:item>
  • <cmdbf:record xmlns="http://school">
  • <student>
  • <identity firstName="Jane" id="02" lastName="Ryerson"/>
  • </student>
  • <cmdbf:recordMetadata>
  • <cmdbf:recordId>02</cmdbf:recordId>
  • </cmdbf:recordMetadata>
  • </cmdbf:record>
  • <cmdbf:instanceId>
  • <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId>
  • <cmdbf:localId>02</cmdbf:localId>
  • </cmdbf:instanceId>
  • </cmdbf:item>
  • <cmdbf:item>
  • <cmdbf:record xmlns="http://school">
  • <student>
  • <identity firstName="Bob" id="01" lastName="Davidson"/>
  • </student>
  • <cmdbf:recordMetadata>
  • <cmdbf:recordId>01</cmdbf:recordId>
  • </cmdbf:recordMetadata>
  • </cmdbf:record>
  • <cmdbf:instanceId>
  • <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId>
  • <cmdbf:localId>01</cmdbf:localId>
  • </cmdbf:instanceId>
  • </cmdbf:item>
  • </cmdbf:nodes>
  • </cmdbf:queryResult>

Test Description:

  1. COSMOS> graphQuery domsr01-xp ExampleMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\ExampleMDR\all-teachers.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp ExampleMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\ExampleMDR\relationship-all-classes.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp ExampleMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\ExampleMDR\teaches-relationship.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp AperiMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\AperiMdr\StorageSystem_all_items.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp AperiMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\AperiMdr\StorageSystem_localid.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp AperiMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\AperiMdr\StorageSystem_display_name.txt

Expected Result:

Test Description:

  1. COSMOS> graphQuery domsr01-xp AperiMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\AperiMdr\StorageSystem_relationship.txt

Expected Result:

Test Description:

  1. COSMOS> COSMOS> graphQuery domsr01-xp TestFederatingCMDB D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\TestFederatingCMDB\all_items.txt

Expected Result:

Using the COSMOS Web User Interface

Data Managers View

Test Description:

  • Layout of the User Interface
  1. Once you have started the COSMOS components, point your web browser to http://localhost:8080/COSMOSUI/?page=cosmos

Expected Result:

  1. The initial page of the COSMOS Web User Interface displays three main panes. The left pane shows a list of data managers that are registered with the broker. The top right pane shows the details view that is initially blank. The bottom right pane shows a properties view that is initially blank.
  2. The pane on the left is the "Data Managers" view. It lists all data managers registered at the broker. There are initially six data managers that are registered with the broker.
    1. A Statistical Data Manager that displays reports on some runtime statistics ("StatDataManager")
    2. A Logging Data Manager that displays reports on log files based on the Common Based Event format. ("LoggingDataManager")
    3. An Example Federating CMDB ("Sample Repository with Registration")
    4. An Example MDR that contains information related to students and teachers ("Sample Repository with Query")
    5. An Asset Repository that contains asset information that is modelled using the Service Modeling Language (SML) ("Resource Repository")
    6. An MDR for making queries on storage management data from Aperi using JDBC ("AperiMdr")
  3. The end user can select a particular data manager to display properties associated with the data manager. The properties are shown in the bottom right pane in the Properties view.

Statistical Data Manager

Test Description:

  • Displaying statistical data sources & Generating the statistical data reports
  1. Expand the "StatDataManager" node in the Data Managers pane to show a list of recorded statistical data sessions
  2. select the collected data "server 33 tomcat1181829221515 CBE" and select "Statistical Report" by right clicking on it

Expected Result:

  1. Generates the statistical report and will be displayed in the "Details" pane
  2. The properties of the selected data collection should be displayed in the Properties pane.

Test Description:

  • Displaying statistical data sources & Generating the statistical data reports
  1. Expand the "StatDataManager" node in the Data Managers pane to show a list of recorded statistical data sessions
  2. select the collected data "server 33 tomcat1181829221515 TomcatSet" and select "Statistical Report" by right clicking on it

Expected Result:

  1. Generates the statistical report and will be displayed in the "Details" pane
  2. The properties of the selected data collection should be displayed in the Properties pane.

Logging Data Manager

Test Description:

  • To query the CBE data manager for a list of log files and generate reports on the log data.
  1. Expand the "LoggingDataManager" node in the left pane to show a list of log files managed by the data manager
  2. Select the log file "access_log.cbe.xml", right click and select "Top 10 Log Report" menu option

Expected Result:

  1. The properties view should show the properties of the log file.
  2. Log report will be generated in the "Details" pane in the top right pane

Test Description:

  • To query the CBE data manager for a list of log files and generate reports on the log data.
  1. Expand the "LoggingDataManager" node in the left pane to show a list of log files managed by the data manager
  2. Select the log file "windows_app_log.cbe.xml" , right click and select "Top 10 Log Report" menu option

Expected Result:

  1. The properties view should show the properties of the log file.
  2. Log report will be generated in the "Details" pane in the top right pane

Using the Registration Example CMDBf (Sample Repository with Registration)

Test Description:

  • To register configuration items with the test Federating CMDB
  1. start the COSMOS UI
  2. right-click on the "Sample Repository with Registration" Data Manager
  3. select "Register Configuration Items..." on the popup menu
  4. In the "Register MDR Configuration Items" window, select the "Example MDR"
  5. Press the "Register" button

Expected Result:

  1. A list of configuration items will be displayed showing status results

Test Description:

  • To Deregister configuration items from the test Federating CMDB
  1. start the COSMOS UI
  2. right-click on the "Sample Repository with Registration" Data Manager
  3. select "Deregister Configuration Items..." on the popup menu
  4. In the "Deregister MDR Configuration Items" window, select the "Example MDR"
  5. Press the "Deregister" button

Expected Result:

  1. A list of configuration items will be displayed showing status results

Test Description:

  1. Sample Repository with Registration
  2. Submit Query

Expected Result:

Test Description:

  1. start the COSMOS UI
  2. right-click on the "Sample Repository with Registration" Data Manager
  3. select "View Metadata" on the popup menu

Expected Result:

  1. Should display MetaData information

Test Description:

  1. Resource Repository
  2. Submit Query

Expected Result:

Test Description:

  1. Resource Repository
  2. View MetaData

Expected Result:

Test Description:

  1. AperiMDR
  2. Submit Query

Expected Result:

Test Description:

  1. AperiMDR
  2. View MetaData

Expected Result:

Test Description:

  1. Sample Repository with Query
  2. Get All Students

Expected Result:

Test Description:

  1. Sample Repository with Query
  2. Get All Teachers

Expected Result:

Test Description:

  1. Sample Repository with Query
  2. Get All Classes

Expected Result:

Test Description:

  1. Sample Repository with Query

3Staff01 Expected Result:

Test Description:

  1. Sample Repository with Query
  2. Staff02

Expected Result:

Test Description:

  1. Sample Repository with Query
  2. Submit Query

Expected Result:

Test Description:

  1. Sample Repository with Query
  2. View MetaData

Expected Result:

End2End Supplement Tests (Negative)

COSMOS Command Line Client : Management Console

Test Description:

  • Configure tomcat port to 9080 (other than default port : 8080) and test the following:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker

Expected Result:

  1. Should display COSMOS prompt without any errors

Test Description:

  • Test Broker registration other than defaul port 8080 (say 9080):
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> broker registerAllDataManagers http://localhost:9080/axis2/services/CosmosServiceFinder

Expected Result:

  1. All DataManagers should successfuly get registered to broker on port 9080

Test Description:

  • Test Broker registration multiple times:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> broker registerAllDataManagers http://localhost:9080/axis2/services/CosmosServiceFinder
  3. COSMOS> broker registerAllDataManagers http://localhost:9080/axis2/services/CosmosServiceFinder

Expected Result:

  1. Under tomcat console window, it should display "Service has already been registered at this broker. No new brokers are registered."

Test Description:

  • Without broker registration, test the following:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> broker getDataManagers

Expected Result:

  1. Should display empty list of DataManagers

Test Description:

  • After succesful broker registration, test the following:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> broker getDataManagers

Expected Result:

  1. Should display all 6 DataManagers registered with broker

Test Description:

  • Without any broker registration, test the following
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> finddatamanagers http://localhost:9080/axis2/services/CosmosServiceFinder

Expected Result:

  1. Should display all 6 DataManagers deployed under tomcat with port 9080

Test Description:

  • Test deregistration of StatDataManager with valid hostname and valid datamanager name :
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> broker deregister domsr01-xp StatDataManager

Expected Result:

  1. Deregistration should be successful

Test Description:

  • Test deregistration of StatDataManager with invalid hostname and valid datamanager name :
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> broker deregister unknown StatDataManager

Expected Result:

  1. Deregistration should fail and should display appropriate error message

Test Description:

  • Test deregistration of StatDataManager with valid hostname and invalid datamanager name :
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> broker deregister domsr01-xp StatDataMgr

Expected Result:

  1. Deregistration should fail and should display appropriate error message

Test Description:

  • Test graphQuery for SMLMDR, with valid hostname,valid DataManager,valid query path:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery domsr01-xp SMLMDR D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\SMLMDR\testInstanceIdQuery.txt

Expected Result:

  1. Query execution should be succesful.

Test Description:

  • Test graphQuery for SMLMDR, with invalid hostname,valid DataManager,valid query path:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery unknown SMLMDR D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\SMLMDR\testInstanceIdQuery.txt

Expected Result:

  1. Query execution should fail and throw appropriate error message.

Test Description:

  • Test graphQuery for SMLMDR, with valid hostname,invalid DataManager,valid query path:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery domsr01-xp StatDataManager D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\SMLMDR\testInstanceIdQuery.txt

Expected Result:

  1. Query execution should fail and throw appropriate error message.

Test Description:

  • Test graphQuery for SMLMDR, with valid hostname,valid DataManager,invalid query path:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery domsr01-xp SMLMDR D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\SMLMDRTest\testInstanceIdQuery.txt

Expected Result:

  1. Query execution should fail and throw appropriate error message.

Test Description:

  • Test graphQuery for SMLMDR, with valid hostname,valid DataManager,valid query path with spaces:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery domsr01-xp SMLMDR "D:\cosmos i10\cosmos-demo\cosmos-client\cmdbfQuery\SMLMDR\testInstanceIdQuery.txt"

Expected Result:

  1. Query execution should be successful

Test Description:

  • Test graphQuery for AperMdr with valid data, with valid Aperi database settings:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery domsr01-xp AperiMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\AperiMdr\StorageSystem_all_items.txt

Expected Result:

  1. Query should execute successfully

Test Description:

  • Test graphQuery for AperMdr with invalid query data, with valid Aperi database settings:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery domsr01-xp AperiMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\AperiMdr\StorageSystem_all_items.txt

Expected Result:

  1. Query execution should fail and display appropriate error message

Test Description:

  • Test graphQuery for AperMdr with valid data, with invalid Aperi database settings:
  1. <cosmos-demo>\cosmos-client\cosmosClient.bat http://localhost:9080/axis2/services/Broker
  2. COSMOS> graphQuery domsr01-xp AperiMdr D:\cosmosi10\cosmos-demo\cosmos-client\cmdbfQuery\AperiMdr\StorageSystem_all_items.txt

Expected Result:

  1. Query execution should fail, with DB Connection error

Using the COSMOS Web User Interface

Test Description

  • Open COSMOSUI with 8090 port (Make sure all COSMOS Components are up and running at this port)
  1. http://localhost:8090/COSMOSUI/?page=cosmos

Expected Result:

  1. Should display all 6 DataManagers properly

Test Description:

  • Open COSMOSUI, Verify Properties of all DataManagers
  1. StatDataManager
  2. LoggingDataManager
  3. Sample Repository with Registration
  4. Sample Repository with Query
  5. Resource Repository
  6. AperiMdr

Expected Result:

  1. All properties should display the correct EPR with port 9080

Test Description:

  • Test StatDataManager, "Statistical Report" generation:
  1. StatDataManager : server 33 tomcat1181829221515 CBE

Expected Result:

  1. Statistical Report should get generated properly

Test Description:

  • Test "LoggingDataManager", Top 10 Log Report generation:
  1. LoggingDataManager : access_log.cbe.xml

Expected Result:

  1. Top 10 Log report should get generated properly

Test Description:

  • Test "Sample Repository with Registration",self registration
  1. Select "Sample Repository with Registration"
  2. Click on "Register Configuration Items..."
  3. Select "Sample Repository with Registration" under registration window

Expected Result

  1. Either it should not be allowed or it should display appropriate error message

Test Description:

  • Test "Sample Repository with Registration",Resource Repository registration
  1. Select "Sample Repository with Registration"
  2. Click on "Register Configuration Items..."
  3. Select "Resource Repository" under registration window

Expected Result

  1. Either registration should not be allowed or it should display appropriate error message

Test Description:

  • Test "Sample Repository with Registration",AperiMdr registration
  1. Select "Sample Repository with Registration"
  2. Click on "Register Configuration Items..."
  3. Select "AperiMdr" under registration window

Expected Result

  1. Either registration should not be allowed or it should display appropriate error message

Test Description:

  • Test Resource Repository, with valid query
  1. select "Resource Repository" and click on "Submit Query"
  2. Provide valid query and submit

Expected Result:

  1. Query should execute successfully

Test Description:

  • Test Resource Repository, with invalid query
  1. select "Resource Repository" and click on "Submit Query"
  2. Provide invalid query and submit

Expected Result:

  1. Query should fail with appropriate error message

Test Description:

  • Test AperiMDR with proper db configuration and with valid query
  1. select "AperiMdr" and create valid query using Query Builder

Expected Result:

  1. Query should execute successfully

Test Description:

  • Test AperiMDR with proper db configuration and with invalid query
  1. select "AperiMdr" and create invalid query using Query Builder

Expected Result:

  1. Query execution should fail and display appropriate error message

Test Description:

  • Test AperiMDR with invalid db configuration and with valid query
  1. select "AperiMdr" and create valid query using Query Builder

Expected Result:

  1. Query execution should fail with db connection error

Test Description:

  • Test "Sample Repository with Query", with valid query
  1. select "Sample Repository with Query"
  2. Create a valid query from query builder and submit it

Expected Result:

  1. Query execution should be successful

Test Description:

  • Test "Sample Repository with Query", with invalid query
  1. select "Sample Repository with Query"
  2. Create an invalid query from query builder and submit it

Expected Result:

  1. Should display Empty Query response under GraphResponseViewer

Basic Operational efficiency tests

Configuration Tests

Test Description:

  • Testing the scenario where COSMOSUI running on windows and all COSMOS services running on Linux
  1. Install COSMOS service components under linux box
  2. Install COSMOSUI,COSMOSReportViewer webapps application under windows
  3. Modify BROKER EPR value under <COSMOSUI>/Configuration.properties file, pointing to linux hostname
  4. From windows, open http://localhost:8080/COSMOSUI

Expected Result:

  1. COSMOS UI should display all 6 Data Managers and all it's operations should work normally

Test Description:

  • Testing the scenario where COSMOSUI running on linux and all COSMOS services running on windows
  1. Install COSMOS service components under windows
  2. Install COSMOSUI,COSMOSReportViewer webapps application under linux
  3. Modify BROKER EPR value under <COSMOSUI>/Configuration.properties file, pointing to windows hostname
  4. From linux, open http://localhost:8080/COSMOSUI

Expected Result:

  1. COSMOS UI should display all 6 Data Managers and all it's operations should work normally

Concurrency Tests

Test Description:

  • Concurrency tests, where multiple COSMOSUI's running on one machine
  1. Install all COSMOS components on windows PC
  2. open 2 COSMOSUI's under IE and 2 COSMOSUI's under Firebox browsers
  3. Perform various test operations - Generating Stat/Log reports on all COSMOSUI's #simultaneously,Executing CMDBf queries on all COSMOSUI's simultaneously

Expected Result:

  1. All COSMOS UI's should work normally and should get appropriate results without any errors

Test Description:

  • Concurrency tests, where multiple COSMOSUI's and multiple COSMOS Command Line Clients running on one machine
  1. Install all COSMOS components on windows PC
  2. open 1 COSMOSUI under IE and 1 COSMOSUI under Firebox browser
  3. open 2 COSMOS Command Line Shells
  4. Perform various test operations - Execute CMDBf queries on all COSMOS Clients simultaneously

Expected Result:

  1. All COSMOS clients should work normally and should get appropriate results without any errors

Volume/Performance Tests

Apache JMeter Tool - Setup Instructions

  1. Open Jmeter window (jmeter-install-dir\bin\jmeter.bat)
  2. On the left side, right click on the ‘Test Plan’ node and select ‘Add->Thread Group’. This inserts one child node called ‘Thread Group’ under ‘Test Plan’.
  3. Select the ‘Thread Group’ node. On the right side for ‘Number of Threads’ text box, give the number of samples.
  4. Right click on ‘Thread Group’ node, and select ‘Add->Sampler->SOAP/XML- RPC Request’. This inserts one child node called ‘SOAP/XML-RPC Request’ under ‘Thread Group’
  5. Select the ‘SOAP/XML-RPC Request’ node. On the right-side, in text box URL: give the URL to which the request to be send. In the ‘Soap/XML-RPC Data’ text area type the ‘SOAP request’
  6. Right click on ‘Thread Group’ node, and select ‘Add->Listener->Summary Report’. This inserts one child node called ‘Summary Report’ under the ‘Thread Group’. We can select our own format for displaying results (summary, table, tree…etc)
  7. Save the test
  8. Now, to run the test, from menu bar select Run->Start for running a test.
  9. Run->Stop for stopping test
  10. The results will be populated in the Listeners that we have added to the test.

Test Description:

  • Using Apache JMeter Tool,testing Broker with samples of 10,50,100,150,200 users simulation
  1. Follow the procedure to create the test, running the test using JMeter.
  2. Provide below SOAP request of Broker to Jmeter tool and run it with users simulation of 10,50,100,150,200.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body><tns:getAllGroups xmlns:tns="http://www.eclipse.org/cosmos/broker" /> </soapenv:Body></soapenv:Envelope>

Expected Result:

  1. Broker requests with all above user samples should work fine with appropriate turn around time

Test Description:

  • Using Apache JMeter Tool,testing StatDataManager with samples of 10,50,100,150,200 users simulation
  1. Follow the procedure to create the test, running the test using JMeter.
  2. Provide below SOAP request of StatDataManager to Jmeter tool and run it with users simulation of 10,50,100,150,200.

Expected Result:

  1. StatDataManager requests with all above user samples should work fine with appropriate turn around time

Test Description:

  • Using Apache JMeter Tool,testing LoggingDataManager with samples of 10,50,100,150,200 users simulation
  1. Follow the procedure to create the test, running the test using JMeter.
  2. Provide below SOAP request of LoggingDataManager to Jmeter tool and run it with users simulation of 10,50,100,150,200.

Expected Result:

  1. LoggingDataManager requests with all above user samples should work fine with appropriate turn around time

Test Description:

  • Using Apache JMeter Tool,testing FederatingCMDB with samples of 10,50,100,150,200 users simulation
  1. Follow the procedure to create the test, running the test using JMeter.
  2. Provide below SOAP requests of FederatingCMDB to Jmeter tool and run it with users simulation of 10,50,100,150,200.

<cmdbf:itemTemplate id="all-items"> </cmdbf:itemTemplate> <cmdbf:relationshipTemplate id="all-relationships"> <cmdbf:sourceTemplate ref="all-items" /> <cmdbf:targetTemplate ref="all-items" /> </cmdbf:relationshipTemplate> </cmdbf:query></soapenv:Body></soapenv:Envelope>

<cmdbf:mdrId /> <cmdbf:itemList> <cmdbf:item> <cmdbf:record xmlns="http://school"> <student> <identity firstName="Mike" id="03" lastName="Lee"> </identity> </student> <cmdbf:recordMetadata> <cmdbf:recordId>03</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>03</cmdbf:localId> </cmdbf:instanceId> </cmdbf:item> <cmdbf:item> <cmdbf:record xmlns="http://school"> <student> <identity firstName="Jane" id="02" lastName="Ryerson"> </identity> </student> <cmdbf:recordMetadata> <cmdbf:recordId>02</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>02</cmdbf:localId> </cmdbf:instanceId> </cmdbf:item> <cmdbf:item> <cmdbf:record xmlns="http://school"> <student> <identity firstName="Bob" id="01" lastName="Davidson"> </identity> </student> <cmdbf:recordMetadata> <cmdbf:recordId>01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:item> <cmdbf:item> <cmdbf:record xmlns="http://school"> <teacher> <identity firstName="Heather" id="staff02" lastName="Reeba"> </identity> </teacher> <cmdbf:recordMetadata> <cmdbf:recordId>staff02</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff02</cmdbf:localId> </cmdbf:instanceId> </cmdbf:item> <cmdbf:item> <cmdbf:record xmlns="http://school"> <teacher> <identity firstName="Dawn" id="staff01" lastName="Johnson"> </identity> </teacher> <cmdbf:recordMetadata> <cmdbf:recordId>staff01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:item> </cmdbf:itemList> <cmdbf:relationshipList> <cmdbf:relationship> <cmdbf:source> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff02</cmdbf:localId> </cmdbf:source> <cmdbf:target> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>03</cmdbf:localId> </cmdbf:target> <cmdbf:record xmlns="http://school"> <class courseCode="PHY01" name="Physics"> <students> <enrolledStudent idRef="02"> </enrolledStudent> <enrolledStudent idRef="03"> </enrolledStudent> </students> <teacher idRef="staff02"> </teacher> </class> <cmdbf:recordMetadata> <cmdbf:recordId>PHY01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>PHY01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:relationship> <cmdbf:relationship> <cmdbf:source> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff02</cmdbf:localId> </cmdbf:source> <cmdbf:target> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>02</cmdbf:localId> </cmdbf:target> <cmdbf:record xmlns="http://school"> <class courseCode="MAT01" name="Mathematics"> <students> <enrolledStudent idRef="01"> </enrolledStudent> <enrolledStudent idRef="02"> </enrolledStudent> </students> <teacher idRef="staff02"> </teacher> </class> <cmdbf:recordMetadata> <cmdbf:recordId>MAT01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>MAT01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:relationship> <cmdbf:relationship> <cmdbf:source> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff02</cmdbf:localId> </cmdbf:source> <cmdbf:target> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>02</cmdbf:localId> </cmdbf:target> <cmdbf:record xmlns="http://school"> <class courseCode="PHY01" name="Physics"> <students> <enrolledStudent idRef="02"> </enrolledStudent> <enrolledStudent idRef="03"> </enrolledStudent> </students> <teacher idRef="staff02"> </teacher> </class> <cmdbf:recordMetadata> <cmdbf:recordId>PHY01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>PHY01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:relationship> <cmdbf:relationship> <cmdbf:source> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff02</cmdbf:localId> </cmdbf:source> <cmdbf:target> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>01</cmdbf:localId> </cmdbf:target> <cmdbf:record xmlns="http://school"> <class courseCode="MAT01" name="Mathematics"> <students> <enrolledStudent idRef="01"> </enrolledStudent> <enrolledStudent idRef="02"> </enrolledStudent> </students> <teacher idRef="staff02"> </teacher> </class> <cmdbf:recordMetadata> <cmdbf:recordId>MAT01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>MAT01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:relationship> <cmdbf:relationship> <cmdbf:source> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff01</cmdbf:localId> </cmdbf:source> <cmdbf:target> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>03</cmdbf:localId> </cmdbf:target> <cmdbf:record xmlns="http://school"> <class courseCode="ECM01" name="Economics"> <students> <enrolledStudent idRef="01"> </enrolledStudent> <enrolledStudent idRef="03"> </enrolledStudent> </students> <teacher idRef="staff01"> </teacher> </class> <cmdbf:recordMetadata> <cmdbf:recordId>ECM01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>ECM01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:relationship> <cmdbf:relationship> <cmdbf:source> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>staff01</cmdbf:localId> </cmdbf:source> <cmdbf:target> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>01</cmdbf:localId> </cmdbf:target> <cmdbf:record xmlns="http://school"> <class courseCode="ECM01" name="Economics"> <students> <enrolledStudent idRef="01"> </enrolledStudent> <enrolledStudent idRef="03"> </enrolledStudent> </students> <teacher idRef="staff01"> </teacher> </class> <cmdbf:recordMetadata> <cmdbf:recordId>ECM01</cmdbf:recordId> </cmdbf:recordMetadata> </cmdbf:record> <cmdbf:instanceId> <cmdbf:mdrId>org.eclipse.cosmos.samples.cmdbf.XMLRepository</cmdbf:mdrId> <cmdbf:localId>ECM01</cmdbf:localId> </cmdbf:instanceId> </cmdbf:relationship> </cmdbf:relationshipList> </cmdbf:registerRequest></soapenv:Body></soapenv:Envelope>

Expected Result:

  1. FederatingCMDB requests with all above user samples should work fine with appropriate turn around time

Test Description:

  • Using Apache JMeter Tool,testing ExampleMDR with samples of 10,50,100,150,200 users simulation
  1. Follow the procedure to create the test, running the test using JMeter.
  2. Provide below SOAP request of ExampleMDR to Jmeter tool and run it with users simulation of 10,50,100,150,200.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <st:query xmlns:st="http://cmdbf.org/schema/1-0-0/datamodel"> <st:itemTemplate id="items" suppressFromResult="false"> <st:recordConstraint> <st:recordType localName="student" namespace="http://schemas.examplemdr.org/schema/ExampleMDR" /> </st:recordConstraint></st:itemTemplate></st:query> </soapenv:Body> </soapenv:Envelope>

Expected Result:

  1. ExampleMDR requests with all above user samples should work fine with appropriate turn around time

Test Description:

  • Using Apache JMeter Tool,testing SMLMDR with samples of 10,50,100,150,200 users simulation
  1. Follow the procedure to create the test, running the test using JMeter.
  2. Provide below SOAP request of SMLMDR to Jmeter tool and run it with user samples of 10,50,100,150,200

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <st:query xmlns:st="http://cmdbf.org/schema/1-0-0/datamodel"> <st:itemTemplate id="cableTemplate"> <st:recordConstraint> <st:propertyValue localName="format" namespace="propertyModel"> <st:equal>RJ45</st:equal> </st:propertyValue> </st:recordConstraint> </st:itemTemplate> </st:query> </soapenv:Body> </soapenv:Envelope>

Expected Result:

  1. SMLMDR requests with all above user samples should work fine with appropriate turn around time

Test Description:

  • Using Apache JMeter Tool,testing AperiMdr with samples of 10,50,100,150,200 users simulation
  1. Follow the procedure to create the test, running the test using JMeter.
  2. Provide below SOAP request of AperiMdr to Jmeter tool and run it with 10,50,100,150,200 users simulation

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <st:query xmlns:st="http://cmdbf.org/schema/1-0-0/datamodel"> <st:itemTemplate id="items" suppressFromResult="false"> <st:recordConstraint> <st:recordType localName="StoragePool" namespace="http://schemas.aperimdr.org/schema/AperiMDR" /> </st:recordConstraint> </st:itemTemplate> </st:query> </soapenv:Body> </soapenv:Envelope>

Expected Result:

  1. AperiMdr requests with all above user samples should work fine with appropriate turn around time

Scalability/Stability Tests

Test Description:

  • Using Apache JMeter Tool,testing ExampleMDR with multiple volumes of test data (data.xml) 1MB, 2MB,2.5MB with user samples of 10,50,100,150,200.
  1. Modify data.xml file to insert test data with 5000,10000,15000 student records
  2. Follow the procedure to create the test, running the test using JMeter.
  3. Provide below SOAP request of ExampleMDR to Jmeter tool and run it with 10,50,100,150,200 users simulation

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <st:query xmlns:st="http://cmdbf.org/schema/1-0-0/datamodel"> <st:itemTemplate id="items" suppressFromResult="false"> <st:recordConstraint> <st:recordType localName="student" namespace="http://schemas.examplemdr.org/schema/ExampleMDR" /> </st:recordConstraint></st:itemTemplate></st:query> </soapenv:Body> </soapenv:Envelope>

Expected Result:

  1. ExampleMDR requests with all above user samples should work fine with appropriate turn around time

Test Description:

  • Scalability tests, with incremental addition of new datamanagers/mdrs
  1. Create duplicate copies of multiple data managers and MDRs (with samples of 6,12,18,24 datamanagers )
  2. Follow the procedure to create the test, running the test using JMeter.
  3. Provide below SOAP requests of various datamanagers to Jmeter tool and run it with 10,50,100,150,200 users simulation
  • URL=
  • Soap Data=

Expected Result:

  1. All requests to various datamanagers should work normally with appropriate turn around time.

References

Retrieved from "https://wiki.eclipse.org/index.php?title=COSMOS_QA_End2End_Tests&oldid=100154"

Back to the top