MAKE A TESTMASTER IMPORT SCRIPT (mktm)


[UBET Installation & Setup][MSE User Guide][UCE User Guide]


CONTENTS


Feature Description


Mktm reads a set of use case graph (UCG) files and generates a script that can be used to create a model inside of TestMaster. Mktm expects to be handed the top file in the use case and recursively reads all of the subordinate UCG files. The output is a TestMaster Import (TMI) file. When the user starts TestMaster, it knows that files named with the ".tmi"  suffix are import files, opens them and builds a model. Mktm can be called directly from the command line in Windows and Solaris. This note tells how to do that.

These notes are for the command line version of mktm.


Running from the command line


During installation, mktm is placed in the bin directory under the UBET installation. On UNIX, the command is named "mktm" and on Windows, it is named "mktm.exe". These notes assume you have placed the ubet bin in your path so you can easily call mktm directly from the command line.  In order to run this script you need to install JRE 1.2.2 (see UBET installation instructions for JRE)

mktm [options] modelName ucgfile [outputfile]

where:
 

modelName the name for the TestMaster project. this is the name that will be passed to TestMaster as the TestMaster project name. It is a required argument.
ucgFile the top level UCG input file. The ucgFile is a top level model in the UBET use case. Depending on the -s flag, this   either becomes the top level model in the new project or it is placed directly under top level model. This is a required argument.
outputFile the file holding the script. The output file contains the resulting script. If it is not supplied, the program writes the script to standard out. TestMaster expects this to have a suffix of ".tmi". If it's not correctly suffixed, the import results are not correct. 
options
-D give timeout information. This prints out "OK" if this not an evaluation version.If it is, it prints out the termination date.
-h print this help message. Causes the usage line to be printed
-check check file reference consistency. Check that subgraphs are always referenced from nodes with the same name and that a node name referencing a file in one graph does not reference a different file in another graph. This option does not build a model, but this check is automatically
performed when a TestMaster model is generated.
-dot dotexe use this version of dot.  This flag and argument gives the location of dot. It is not needed if the UBET bin is in your path. dotexe = full path to dot.exe
-c include comments in the output file. This causes comments to be inserted into the script file. The comments document the source file names of the resulting TestMaster models along with any name aliasing that might have been done to make names   acceptable to TestMaster.
-s ModelCall Create a top model containing a test setup modelcall and a UBET model call named ModelCall

Using the -s flag causes an additional top level   in the resulting TestMaster project. That model is called "modelName" from the command line and it contains two model calls, one named "TestSetup" and the other named the value of the "ModelCall" argument. The   "ModelCall" model contains the original UBET model. 



Example


If you had a UBET model that looked like this:

wpe1.jpg (4051 bytes)

calling mktm thus "mktm Fred top.ucg Fred.tmi", results in a TestMaster model that looks like this (assuming lower level
stay the same:

wpe2.jpg (3423 bytes)

If mktm is call this way: "mktm -s Joe Fred top.ucg Fred.tmi", the resulting TestMaster model looks like this:

wpe3.jpg (6366 bytes)

The TestSetup model, can then be used in TestMaster to set up initialization operations.



Restrictions


The Mktm script enforces several restrictions that are not in UBET.  The following conditions are not allowed in TestMaster and will result in errors.

No different references to the same file


wpe5.jpg (6366 bytes)

 No same named nodes referencing different files

 


pos_lucent.gif (1187 bytes)