RADE |
Java Unit Test Manager |
mkodtRuns test objects |
| Quick Reference | ||
mkodt Runs java test objects
mkodt can be run in contextual or descriptive mode:
- Contextual mode: mkodt is run from a framework directory and applies to test objects of this framework
mkodt [-htX] -D [ -s shell | -a ]- Descriptive mode: mkodt is run from any directory and applies to the workspace and frameworks passed using appropriate options
mkodt[-chkqStX] [-d wsabspath [-F framework] | -W wsrelpath | [-a| -L scriptlist1 | -l scriptlist2 -s shell]] [-NOMaxTime] [-NoPert] [-o output] [-p path] [-r rtpath] [-UpdateInit]
[Top]
Runs java test objects, that is, shell scripts that launch java applications delivered in test frameworks. Using its options, mkodt gives the choice of running one test object or all the test objects found either in a given framework or workspace.
mkodt is available with mkmk commands, and can be accessed after running the
mkmk_profileoradl_profilecommand.
[Top]
mkodt accepts the following options:
-aReplays all tests objects for a workspace, a framework, or a directory TestCases or SwitchTestCases -DSets the display mode for debug purposes, that is, opens a window ("xterm" or "DOS") for interactive testing. This window is opened in the same environment that the one used by the test object, thus it is possible to check for the value of environment variables. Available in contextual mode only -d wsabspathSpecifies the workspace root directory using an absolute path -F frameworkSpecifies a framework directory or a list of framework directories of the workspace -hDisplays the mkodt help -kKeeps the temporary directory set using ADL_ODT_TMP-L scriptlist1Reads the file scriptlist1to get a list of shell scripts to execute. These shell scripts can be in different frameworks of the workspace.scriptlist1must have the following format:FW1 Type ODTName1 FW2 Type ODTName2 FW3 Type ODTName3where
Typecan be eitherTestCasesorSwitchTestCases. If the path of thescriptfileis not specified, this file must be in the current directory or in the workspace root directory-l scriptlist2Reads the file scriptlist2to get a list of shell scripts to execute.scriptlist2must have the following formatODTName1 ODTName2 ODTName3If the path of the
scriptfileis not specified, this file must be in the current directory or in the workspace root directory-NOMaxTimeDisables the supervision of the ODT's execution time -NoPertDisables the pertinence measure for an ODT -o outputSpecifies an output directory and sets the ADL_ODT_OUTvariable. Results of mkodt ( .traces and .mkodt_results files) are generated in the directoryOutput/Framework.tst/FunctionTests/Output/OS, where OS is a directory the name of which is an acronym that depends on the operating system. Refer to [1] to get the current list of operating systems supported and associated acronyms.-p pathSpecifies the directory pathname concatenation where the module or EXE are searched for, and initializes ADL_ODT_CONCATENATION(used by theWhichDircommand). Directory pathnames are separated by a:(colon) with Unix and a;(semicolon) with Windows-qQuiet mode : no user information -r rtpathSpecifies the directory pathname concatenation where the module or EXE are searched for without changing the ADL_ODT_CONCATENATIONvalue. Directory pathnames are separated by a:(colon) with Unix and a;(semicolon) with Windows-SSearches test objects in SwitchTestCases instead of TestCases -s shellLists the shell script names to run -tReports the time spent for the execution -UpdateInitDeletes the directory generated by ODTInit-W wsrelpathSpecifies the workspace root directory using a relative path from the $HOMEdirectory. Valid with UNIX only-XForces output display. By default, program's outputs are not displayed, and this option forces them to be displayed
[Top]
- To run the ODTs whose shells are listed in the shell file in contextual mode.
mkodt -D -s shell- To run, with Unix only, all ODTs in a given workspace by specifying a relative directory
mkodt -a -W CAAWorkspace- To run, with Unix only, all ODTs of a given framework of a given workspace by specifying a relative directory
mkodt -a -W CAAWorkspace -F fwname- To run all ODTs in a given workspace by specifying an absolute directory
Unix mkodt -a -d /u/users/psr/CAAWorkspaceWindows mkodt -a -d e:\users\psr\CAAWorkspace- To run all ODTs in a given workspace by specifying an absolute directory, and generate output in a given directory
Unix mkodt -a -d /u/users/psr/CAAWorkspace -o /u/users/psr/outputWindows mkodt -a -d e:\users\psr\CAAWorkspace -o e:\users\psr\output- To run all ODTs in a given workspace by specifying the workspace absolute directory, and generate output in a given directory, using the programs located in a local directory and resetting the
ADL_ODT_CONCATENATIONvariable to this directory
Unix mkodt -d /u/lego/CXR4/BSF -a -o /u/users/psr/output -p /u/users/psr/steplib/CXR4/LocalWSWindows mkodt -d \\renoir\CXR4\BSF -a -o E:\users\psr\output -p e:\steplib\CXR4\LocalWSThe common content of the
ADL_ODT_CONCATENATIONand of the runtime concatenation used is either/u/users/psr/steplib/CXR4/LocalWSwith Unix ore:\steplib\CXR4\LocalWSwith Windows.- To run all ODTs in a given workspace by specifying the workspace absolute directory, and generate output in a given directory, using the programs located in a local directory without resetting the
ADL_ODT_CONCATENATIONvariableThe content of the
Unix mkodt -d /u/lego/CXR4/BSF -a -o /u/users/psr/output -r /u/users/psr/steplib/CXR4/LocalWSWindows mkodt -d \\renoir\CXR4\BSF -a -o E:\users\psr\output -r e:\steplib\CXR4\LocalWSADL_ODT_CONCATENATIONvariable is unchanged and the directory in which the programs are searched for is either/u/users/psr/steplib/CXR4/LocalWSwith Unix ore:\steplib\CXR4\LocalWSwith Windows.
[Top]
mkodt uses the following environment variables:
ADL_ODT_CONCATENATIONContains a directory concatenation used by the WhichDircommandADL_ODT_JREReferences the JRE (Java RunTime Environment) where the ODT is going to be replayed: ADL_ODT_JRE can be set to:
- msjre_a (Windows) (Microsoft's JRE available on Windows)
- sunjre_a (Windows and SunOS) (SUN's JRE available on Windows and SunOS)
- ibmjre_a (AIX) (IBM's JRE available on AIX)
- hpjre_a (HP) (HP's JRE available on HP)
If this variable is not set before launching mkodt, it will be set by default to:
- Replay on Windows: sunjre_a
- Replay on SunOS: sunjre_a
- Replay on AIX: ibmjre_a
- Replay on HP: hpjre_a
ADL_ODT_INContains a directory where all data needed as input for a program is stored ADL_ODT_NULLContains a special file name that can be used to redirect outputs from a program ( /dev/nullwith Unix orNULwith Windows)ADL_ODT_OUTContains an output directory where any output data can be stored ADL_ODT_REFContains a directory where reference data is stored. Reference data is used as a reference to compare program output ADL_ODT_TMPContains a temporary directory, for instance /tmpwith Unix andC:\TEMPwith WindowsMKMK_LST_RTVContains a runtime path concatenation. Corresponds to -roptionMKODT_SUPENVContains a shell script path that will be run before the ODT shell script. Use this variable to set an environment extension. By default, if this variable is not set, mkodtlooks forMKODT_SUPENV_($ADL_FR_CATIA)file in$PATHODT_MAX_TIME_COEFFContains a percentage to apply to the max_time value:
max_time = max_time*$ODT_MAX_TIME_COEFF/100ODT_MAX_TIMEContains the maximum time that the ODT can run before being stopped, expressed in xxx (max_time) ODT_PERTINENCEContains the pertinence measure ability. Valid values are:
YesEnables the pertinence measure NoDisables the pertinence measure ODT_PERTINENCE=Nocorresponds to the-NoPertoptionOPTION_FOR_SETCATENVContains additional options for setcatenv (set the CATIA environment) WSROOTContains the workspace directory containing the test objects to run
[Top]
Possible exit status values are:
0 Successful completion >0 Failure because any of the following
[Top]
| [1] | Building and Launching a CAA V5 Use Case |
| [Top] | |
| Version: 1 [March 2001] | Document created |
| [Top] | |
Copyright © 2000, Dassault Systèmes. All rights reserved.