Dotnet Vs Test Step
A .NET vstest step to run .NET VSTest
Example. Runs dotnet vstest command to run selected tests by names from the specified assemblies
buildType {
// Other Build Type settings ...
steps {
// Other Build Steps ...
dotnetVsTest {
assemblies = "path\to\assemblies\*.dll"
excludedAssemblies = "path\to\assemblies\ExcludedTests.dll"
version = DotnetVsTestStep.VSTestVersion.V17
filter = testName {
names = """
Test0
Test1
Test2
""".trimIndent()
}
settingsFile = "MyProjectTestsSettings.runsettings"
logging = DotnetVsTestStep.Verbosity.Normal
runInIsolation = true
platform = DotnetVsTestStep.Platform.x64
}
Content copied to clipboard }
}See also
Types
Properties
Specify paths to test assemblies. Wildcards are supported.
Optional collection of build step execution conditions
Specifies coverage tool to use
Specifies which Docker image to use for running this build step. I.e. the build step will be run inside specified docker image, using 'docker run' wrapper.
Specifies which Docker image platform will be used to run this build step.
If enabled, "docker pull image" will be run before docker run.
Additional docker run command arguments
Specify paths to excluded test assemblies. Wildcards are supported.
Build step execution mode
The filter type used while test run
Specifies which pull policy will be used with the specified image at each pod's execution.
Specify logging verbosity
Rerun failed tests until they pass or until the maximum number of attempts is reached.
Target platform architecture to be used for test execution
Whether TeamCity should run tests in an isolated process
The path to the run settings configuration file.
Whether TeamCity should run tests in a single session
VSTest version to use
Build working directory for script, specify it if it is different from the checkout directory.
Functions
Deletes all configured build step conditions
Configures build step conditions
Copies parameters of this object to the specified target
A list of records, each field of an item stored as a parameter of its own: parameter f of the n-th item, counting from 1, is stored as name.n.f. A script fills the list in the block of the parameter, see RecordList.
A record, each field stored as a parameter of its own: parameter f of the record is stored as name.f. A script fills the record in the block of the parameter; a record without parameters stores nothing.
Validates this object and reports found errors to the provided consumer