Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions

Execute test code in UI thread for Windows store apps.

Gets or sets the that should be used to invoke the UITestMethodAttribute. If none is provided, it will try to use the Microsoft.UI.Xaml.Window.Current.DispatcherQueue, which only works on UWP.

Executes the test method on the UI Thread.

The test method. An array of instances. Throws when run on an async test method.

TestContext class. This class should be fully abstract and not contain any members. The adapter will implement the members. Users in the framework should only access this via a well-defined interface.

Gets test properties for a test.

Gets or sets the cancellation token source. This token source is cancelled when test timesout. Also when explicitly cancelled the test will be aborted

Gets Fully-qualified name of the class containing the test method currently being executed

This property can be useful in attributes derived from ExpectedExceptionBaseAttribute. Those attributes have access to the test context, and provide messages that are included in the test results. Users can benefit from messages that include the fully-qualified class name in addition to the name of the test method currently being executed.

Gets the fully specified type name metadata format.

Gets the fully specified method name metadata format.

Gets the Name of the test method currently being executed

Gets the current test outcome.

Used to write trace messages while the test is running

formatted message string

Used to write trace messages while the test is running

format string the arguments

Used to write trace messages while the test is running

formatted message string

Used to write trace messages while the test is running

format string the arguments

Used to specify deployment item (file or directory) for per-test deployment. Can be specified on test class or test method. Can have multiple instances of the attribute to specify more than one item. The item path can be absolute or relative, if relative, it is relative to RunConfig.RelativePathRoot.

[DeploymentItem("file1.xml")] [DeploymentItem("file2.xml", "DataFiles")] [DeploymentItem("bin\Debug")] Putting this in here so that UWP discovery works. We still do not want users to be using DeploymentItem in the UWP world - Hence making it internal. We should separate out DeploymentItem logic in the adapter via a Framework extensibility point. Filed https://github.com/Microsoft/testfx/issues/100 to track this.

Initializes a new instance of the class.

The file or directory to deploy. The path is relative to the build output directory. The item will be copied to the same directory as the deployed test assemblies.

Initializes a new instance of the class

The relative or absolute path to the file or directory to deploy. The path is relative to the build output directory. The item will be copied to the same directory as the deployed test assemblies. The path of the directory to which the items are to be copied. It can be either absolute or relative to the deployment directory. All files and directories identified by will be copied to this directory.

Gets the path of the source file or folder to be copied.

Gets the path of the directory to which the item is copied.