Learning More about WS WAVE Wbem Agent Validation Environment
The WS WBEM Agent Validation Environment (WAVE) product is a test infrastructure that allows a user to validate the proper behavior of a target agent system. It allows a user to properly validate a Profile, which is a specification that defines the CIM model and associated behavior for a management domain. When properly implemented, a profile allows a management client to reliably perform the management tasks related to the management domain in a heterogeneous computing environment.
The WS WBEM Agent Validation Environment (WAVE) product is a Java-based application. The following are required before you can use the WS WBEM Agent Validation Environment product:
|J2SE™ 1.5.x JRE||The WS WBEM Agent Validation Environment will run on any platform that supports the Sun JVM 1.5.x which can be obtained from the http://java.sun.com website.|
|JAVA_HOME||The JAVA_HOME environment variable must be set prior to using the WS WBEM Agent Validation Environment product.|
How WAVE works?
The WAVE test infrastructure is a set of Java based libraries and applications that is used to validate the conformance for a particular specification on a target WBEM server using a designated protocol. It runs on different types of Test Drivers.
- The Profile Test Driver validates the proper implementation of a profile on a target Agent system.
- The Protocol Test Driver validates the proper implementation of a session level protocol on a target Agent system.
- The Generic Test Driver validates the proper implementation of the CIM Specification on a target Agent system.
***Other Test Drivers may be added to WAVE in the future.
To run WAVE, a Project File must be first created. that designates the Test Driver to use, the Test Cases to run, the Profiles to test and many other test configuration parameters.
A Project file identifies which of the profiles listed in ProfileList.xml are tested against a target WBEM server using a designated management protocol when using a Profile Test Driver.
The Profile Test Driver is driven by a ProfileDefinition file called a Profile XML Format (PXF) file that identifies the classes, properties, methods, use cases and indications that WAVE will test for a particular profile. PXF files are grouped by Initiative. (Dash, CDN, SMASH, SMI)
Testcases are listed in UsecaseList.xml which WAVE can run against any profile or specific tests (called use cases) against a specific profile.
WAVE writes test results to Log Files in XML format and converts the test result information into HTML format.
***Currently, WAVE supports the CIM-XML and WS-Management management protocols using HTTP or HTTPS. Other protocol support may be added to WAVE in the near future.
By default, the wave program can be found at:
The wave utility can be invoked by typing wave at the command prompt.
C:\> cd \Program Files\ws\wave\bin
C:\> wave -h
WAVE [options] project
Copyright (c) 2008 WS, Inc.
-h Display this usage statement
-q Quiet mode
-v Display the version information
project The project File
C:\> cd \Program Files\ws\wave\bin
C:\> wave myproject.xml
***This example on Windows, runs the project file myproject.xml. Output results will be written to the directory Results0
Examining WAVE Test Results
A set of directories and files containing the test results in XML and HTML format are created each time WAVE is run. For each test run, test results are further organized by target agent system and test driver. Results are further broken down based on the type of test driver.
To examine the test results, open index.html in the test report directory. For the first test run, WAVE creates test report directory Results0. For the next test run, WAVE creates test report directory Results1, and so on.
The top level test report index.html page shows a Summary Report.
To get further test result information about a profile, click on the Profile Name link as shown in Screen 1. For example, clicking on the DMTF Base Desktop and Mobile 1.0.0 link would show a page similar to the following:
Here, summary test results for the DTMF Base Desktop and Mobile 1.0.0 Profile is shown. The total number of tests run was 438 of which 429 passed and 9 failed. The Class Summary table shows the summary results of the CIM classes that WAVE tested. This page shows that one or more tests on the CIM_ComputerSystem class failed. This class must be implemented as defined by the profile specification DSP1058 at Section 10.1, Line 545. There was only one instance of CIM_ComputerSystem.
***WARNING: The type and organization of the information in this page may change from one version of WAVE to the next.