ViewArticle

[Collapse]Automated Build Studio/viewarticle/9302/
 [Expand]Introduction/viewarticle/9304/
 [Expand]Getting Started/viewarticle/9312/
 [Expand]Working With Automated Build Studio/viewarticle/9325/
 [Collapse]Operations Reference/viewarticle/9623/
   Common Operation Properties/viewarticle/9386/
  [Expand].NET Tools/viewarticle/9933/
  [Expand]ADO/viewarticle/10368/
  [Expand]Amazon EC2/viewarticle/22737/
  [Expand]Archivers/viewarticle/9794/
  [Expand]Authenticode/viewarticle/10217/
  [Expand]Build Tools/viewarticle/10156/
  [Expand]Borland Compilers/viewarticle/9679/
  [Expand]Burn CD/DVD/viewarticle/10301/
  [Expand]Communication/viewarticle/10094/
  [Expand]Concurrent Versions System/viewarticle/9634/
  [Expand]Embarcadero Compilers/viewarticle/63530/
  [Expand]Encrypting File System/viewarticle/10352/
  [Expand]Execute/viewarticle/10365/
  [Expand]Files and Directories/viewarticle/10107/
  [Expand]Frequently Used/viewarticle/10195/
  [Expand]FTP/viewarticle/10093/
  [Expand]Help Compilers/viewarticle/10109/
  [Expand]HTTP/viewarticle/10092/
  [Expand]Installers/viewarticle/9795/
  [Expand]Interactive/viewarticle/9504/
  [Expand]Internet Information Services (IIS)/viewarticle/9964/
  [Expand]Issue Tracking/viewarticle/9472/
  [Expand]JediVCS/viewarticle/9949/
  [Expand]Logging/viewarticle/10210/
  [Expand]Mercurial/viewarticle/10353/
  [Expand]Microsoft Compilers/viewarticle/9676/
  [Expand]Microsoft Compilers for Smart Device/viewarticle/9675/
  [Expand]Microsoft Hyper-V/viewarticle/42211/
  [Expand]Microsoft Source Server/viewarticle/10291/
  [Expand]Microsoft SQL Server/viewarticle/9882/
  [Expand]Microsoft Virtual PC/viewarticle/10015/
  [Expand]Microsoft Virtual Server/viewarticle/9508/
  [Expand]Microsoft Visual SourceSafe/viewarticle/9626/
  [Expand]Misc/viewarticle/10263/
  [Expand]MySQL/viewarticle/9885/
  [Expand]Oracle/viewarticle/10203/
  [Expand]Other Compilers/viewarticle/9677/
  [Expand]Patch Management/viewarticle/10167/
  [Expand]Perforce/viewarticle/9624/
  [Expand]Prepare Code/viewarticle/10134/
  [Expand]PsTools/viewarticle/9720/
  [Expand]PVCS/viewarticle/9632/
  [Expand]Rational ClearCase/viewarticle/9629/
  [Expand]Read/Write/viewarticle/10241/
  [Expand]Remote Macro Execution/viewarticle/9369/
  [Expand]Serena Dimensions/viewarticle/10364/
  [Expand]SmartBear and AutomatedQA Tools/viewarticle/10098/
  [Expand]Source Code Tools/viewarticle/10194/
  [Expand]SourceGear Vault/viewarticle/9625/
  [Expand]SourceOffSite/viewarticle/9633/
  [Expand]Standard/viewarticle/10212/
  [Expand]StarTeam/viewarticle/9622/
  [Expand]String Manipulation/viewarticle/10308/
  [Expand]Subversion/viewarticle/9628/
  [Expand]Surround SCM/viewarticle/9621/
  [Expand]Team Coherence/viewarticle/9471/
  [Expand]Team Foundation Version Control/viewarticle/9608/
  [Collapse]Unit Tests/viewarticle/10115/
    Run JUnit Test Operation/viewarticle/10116/
    Run MSTest Operation/viewarticle/9891/
    Run NUnit Test Operation/viewarticle/9992/
    TypeMock Runner Operation/viewarticle/10373/
  [Expand]User Interface Actions/viewarticle/10346/
  [Expand]VMware Server/viewarticle/10008/
  [Expand]VMware vSphere/viewarticle/42215/
  [Expand]VMware Workstation/viewarticle/9913/
  [Expand]Wait/viewarticle/9994/
  [Expand]WMI/viewarticle/10136/
  [Expand]XML/viewarticle/9702/
 [Expand]Technical Support and Resources/viewarticle/9314/
 [Expand]Other Tools for Improving Your Build Processes/viewarticle/42205/
Updated: 1/9/2014 Applies To: Automated Build Studio 6 Rating: No votes Click to rate: PoorNot badAverageGoodExcellent
Unit Tests Operations

TypeMock Runner Operation

The TypeMock Runner operation runs TypeMock Isolator to perform unit testing of the specified application.

Requirements

In order for the operation to be executed successfully, TypeMock Isolator must be installed on your computer, and the Tools dialog must contain a valid reference to the TypeMock Runner executable (TMockRunner.exe) residing on your computer.

Child Operations

The operation cannot have child operations.

Operation Properties

The operation properties are organized into the following pages:

Properties

This page contains properties common for all operations. For more information on them, see Properties That Are Common for All Operations. We would like to draw your attention to the Timeout property on this page:

Timeout

The purpose of this property is to stop TMockRunner if it is working too long and probably has frozen. When the operation execution reaches the timeout limit, Automated Build Studio closes the TMockRunner instance started by the operation. Using the operation's Timeout property is one of two ways to set the timeout limit for operations. Besides the operation's Timeout property, you can use the timeout common for all operations in the macro (see Macro Properties Dialog).

TMock Runner Details

Program file

Required. Specifies the name (with the full path) of the executable file to be tested. You can either enter the executable file's name with the full path manually or specify a variable or constant that holds the executable name. You can also click the ellipsis button and choose the executable file in the standard Open file dialog. To specify the property value, you can also use the single-lined scripts.

Arguments

Optional. Specifies the argument(s) you want to send to the tested application. You can either enter the argument manually or specify an existing variable or constant that holds the argument. You can also specify the list of the arguments that are to be sent. To separate multiple arguments, use semicolons. You can either enter the arguments list manually or specify a variable or constant that holds the arguments list. Also, you can click the ellipsis button and use the File List Field Editor to form the argument list. To specify the property value, you can also use the single-lined scripts.

Link a code-coverage tool

Optional. Specifies the code-coverage tool to be linked with TypeMock Isolator for unit testing. You can either enter the tool name manually or specify a variable or constant that holds the tool name. To specify the property value, you can also use the single-lined scripts. The code-coverage tool must be installed on your computer and supported by TypeMock Isolator, otherwise, the operation fails. To check what code-coverage tools TypeMock Isolator supports, see its documentation.

Code-coverage is run before test application

If checked, the code-coverage tool is launched before TypeMock Isolator starts testing the application.

Path to log directory

Specifies the path to the directory where TypeMock Isolator stores the log files created during the unit testing. You can either enter the path manually or specify a variable or constant that holds the path. You can also click the ellipsis button and choose the needed log directory location in the standard Browse For Folder dialog. To specify the property value, you can also use the single-lined scripts.

Verbose log level

Specifies the level of details the TypeMock runner will fill the log with during the testing. It can take values from 0 to 9. If the log level value is 0, no log is created by TypeMock Isolator.

Target .NET version

Specifies the framework version that is used for unit testing. You can choose the version from the drop-down list.
Output

None

If checked, no output is shown after testing.

Log

If checked, TypeMock Isolator creates a log file containing results of the unit testing and stores the file in the directory specified by the Path to log directory parameter. The path to the log file is shown in the Log panel.

Variable

Specifies the variable to store the path to the file containing unit test results.

File

Specifies the path to the file that stores paths to files containing unit test results. You can either enter the path manually or specify a variable or constant that holds the file path. You can also click the ellipsis button and choose the file in the standard Save As dialog. To specify the property value, you can also use the single-lined scripts.

Append to the file

If checked, a new path to the file containing test results is appended to the end of the file specified by the File parameter.

Remarks

You can use variables and constants to set values of operation properties. When specifying the variable (or constant) name, enclose it in the % symbols, for instance, %VariableName%. See Using Variables and Constants in Operation Properties.

See also
Unit Tests Operations | Specifying Operation Properties


© 2018 SmartBear Software. All rights reserved.
Email Send feedback on this document