User guide

98
Parameter
Variable
Mandatory?
Description
-BuildNumber
No*
Allows the user to specify the build
number whose drop location will
contain the Automated Tests. This
parameter can only be used under
MTM 2012. If defined, the
BuildDefinition parameter must also
be specified. If not specified, the field
"build," visible in the details of a test
run, will not be affected by the test
run.
-SettingsName
No
Allows the user to specify the settings
to use for the test run. If not specified,
the default one will be used.
-TestRunWaitDelay
No
Allows the user to specify the delay, in
seconds, between each call to the test
controller. This is required to allow
the test run to complete before
processing the test results. If not
specified, it will default to 10 seconds.
-InconclusiveFailsTests
N/A
No
When this flag is set, the existence of
inconclusive tests will fail the
deployment. By default,
an inconclusive test will not fail the
deployment.
RemoveIncludeParameter
N/A
No
When this flag is set, the /include
parameter will not be appended to
the test creation command. This
means that any tests that have a
status different than Active will not be
included in the test run.
If the Automated Tests are included in the same build process as the application being deployed, it is possible to use
Metadata as the variable value and it will be automatically replaced at release time. The following is the currently
available Metadata that can be used with Configuration Variables.
Variable
Variable value Metadata
BuildDirectory
$(PackageLocation)
BuildNumber
$(BuildNumber)
BuildDefinition
$(BuildDefinition)