|
ObjectBroker ActiveX Studio (Agent) Testing Overview
The ObjectBroker ActiveX Studio (Agent) application is a component
of the ObjectBroker Desktop Connection that provides DocObject and ActiveX
control views of ObjectBroker objects. It runs on Windows '95 or WNT V4.0
systems and has a graphical user interface which allows users to build up
views of objects using common windows controls.
The testing of the Agent is performed with Rational Software's
Visual Test tool. Testing is aimed at the most frequently used
functionality, with no attempt at complete code coverage. Testing of this
application was halted in order to refocus on other ObjectBroker components,
so some desired tests are not complete. Testing was last attempted on bridge
baselevel X0956, which occured between baselevels 4 and 5. A summary of the
testing status is available in the file AgentTestStatus.doc.
Software requirements to run the Agent tests:
---------------------------------------------
- Rational Software Visual Test V4.0 or later
- Windows NT V4.0 or MS Windows '95
- ObjectBroker V2.7v11 or later, Developer's version
- ObjectBroker Desktop Connection
- A running copy of the following Corba servers:
- SAS (Swiss Army Server, which supports all datatypes)
available in directory: \\obbfs1\obbcom\peterc\agent\server
- POS (Point of Sale) available in directory
\\obbfs1\obbcom\Mike Rosen\ActiveX. There is a labnotes.txt
file which explains how to build POS.
- Visual C++ to build the SAS server
- note: a few include file routines were extracted from TestNow V2.0
(ST Labs). We have license to include the software, however we used
almost none of it.
Installing the Agent tests:
---------------------------
- The source code is available under the directory tree
\\obbfs1\obbcom\peterc\agent\XOLEsuite
If you have sourcesafe set up, you can also access the tests under
\\oopman\vss
Running the Agent tests:
------------------------
- Copy the entire test tree from \\obbfs1\obbcom\peterc\agent\ to
a directory on your system.
- Build the SAS server by running an NMAKE in the server directory.
- Start the SAS server in an MS Dos Window (SASS.EXE)
- Build and start the POS server (TBD)
- Start Visual Test
- Open the XOLE project from the top level directory where you
installed the Agent tests. Do this by selecting "Open Workspace"
and XOLE.VTP. Note that the .VTP is preferable to the .MDP file initially,
because it does not contain hard wired directory paths.
- Expand the test hierarchy within "TestView" to reveal all tests.
- Stop working in other windows. You do not have to close out other
applications, but you should stop interacting with them, because focus
changes can destroy a test run.
- To run an individual test, select the testname from the "TestView"
window, and select menu item Test/Go. Sit back and watch with your
hands off the system.
- If you prefer to run a collection of tests, start the Suite Manager
tool via the Test menu. The Suite Manager allows you to select
several tests, and run them in sequence. Sit back and watch with your
hands off the system.
Test Organization:
------------------
Tests are organized by three levels: test folders, test cases, and scenarios.
Test folders equate to directory folders, tests cases equate to '.mst' source
files, and scenarios are subcomponents of the test cases.
Test Design:
------------
The tests are written with a primary goal of long term maintainability.
Generally, any common user interaction such as opening an object has a
utility routine to accomplish that task. This approach saves maintainers
from having to edit scores of tests to compensate for a functionality
change, for example in the Open Object dialog box. Visual Test is an
interpreted language, so all the utility routines are embedded in include
files, as specified below.
Most tests are directly associated with menu items within the Agent (XOLE)
application. There are also tests defined for datatypes testing. Datatypes
testing confirms that the agent can handle each of the datatypes which the
bridge can handle: simple data types, arrays, sequences, unions, structures,
etc. As of 3/10/97, only simple datatypes are implemented in the Agent, and
therefore they are the only datatypes tested.
Include files (major files only):
---------------------------------
ControlAddUtils: utility routines specific to adding controls to a perspective
DBLoad.inc: Sets up several tables for use with datatype testing.
DBRtns.inc: Utility routines to access the tables defined in dbload.inc.
For example, the utilities simplify getting the 4th parameter
to the SmplIn method of the SMPL_PAR interface of the SAS
object.
DBtypes.inc: structure definitions for datatype tables.
MBWizUtil.inc: utility routines specific to the Method Binding Wizard.
mlb.inc: metadata library utility routines.
perspecUtil.inc: utility routines specific to managing perspectives.
xolemain.inc: constants, constants, constants.
xoleutil.inc: many utility routines, often crossing areas of functionality.
|