assemblies/MSTest.TestFramework.1.2.0/lib/uap10.0/Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions.XML
|
<?xml version="1.0"?>
<doc> <assembly> <name>Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions</name> </assembly> <members> <member name="T:Microsoft.VisualStudio.TestTools.UnitTesting.DeploymentItemAttribute"> <summary> 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. </summary> <example> [DeploymentItem("file1.xml")] [DeploymentItem("file2.xml", "DataFiles")] [DeploymentItem("bin\Debug")] </example> <remarks> 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 extensiblity point. Filed https://github.com/Microsoft/testfx/issues/100 to track this. </remarks> </member> <member name="M:Microsoft.VisualStudio.TestTools.UnitTesting.DeploymentItemAttribute.#ctor(System.String)"> <summary> Initializes a new instance of the <see cref="T:Microsoft.VisualStudio.TestTools.UnitTesting.DeploymentItemAttribute"/> class. </summary> <param name="path">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.</param> </member> <member name="M:Microsoft.VisualStudio.TestTools.UnitTesting.DeploymentItemAttribute.#ctor(System.String,System.String)"> <summary> Initializes a new instance of the <see cref="T:Microsoft.VisualStudio.TestTools.UnitTesting.DeploymentItemAttribute"/> class </summary> <param name="path">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.</param> <param name="outputDirectory">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 <paramref name="path"/> will be copied to this directory.</param> </member> <member name="P:Microsoft.VisualStudio.TestTools.UnitTesting.DeploymentItemAttribute.Path"> <summary> Gets the path of the source file or folder to be copied. </summary> </member> <member name="P:Microsoft.VisualStudio.TestTools.UnitTesting.DeploymentItemAttribute.OutputDirectory"> <summary> Gets the path of the directory to which the item is copied. </summary> </member> <member name="T:Microsoft.VisualStudio.TestTools.UnitTesting.AppContainer.UITestMethodAttribute"> <summary> Execute test code in UI thread for Windows store apps. </summary> </member> <member name="M:Microsoft.VisualStudio.TestTools.UnitTesting.AppContainer.UITestMethodAttribute.Execute(Microsoft.VisualStudio.TestTools.UnitTesting.ITestMethod)"> <summary> Executes the test method on the UI Thread. </summary> <param name="testMethod"> The test method. </param> <returns> An array of <see cref="T:Microsoft.VisualStudio.TestTools.UnitTesting.TestResult"/> instances. </returns> Throws <exception cref="T:System.NotSupportedException"> when run on an async test method. </exception> </member> <member name="T:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext"> <summary> 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. </summary> </member> <member name="P:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.Properties"> <summary> Gets test properties for a test. </summary> </member> <member name="P:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.FullyQualifiedTestClassName"> <summary> Gets Fully-qualified name of the class containing the test method currently being executed </summary> <remarks> 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. </remarks> </member> <member name="P:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.TestName"> <summary> Gets the Name of the test method currently being executed </summary> </member> <member name="P:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.CurrentTestOutcome"> <summary> Gets the current test outcome. </summary> </member> <member name="M:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.WriteLine(System.String)"> <summary> Used to write trace messages while the test is running </summary> <param name="message">formatted message string</param> </member> <member name="M:Microsoft.VisualStudio.TestTools.UnitTesting.TestContext.WriteLine(System.String,System.Object[])"> <summary> Used to write trace messages while the test is running </summary> <param name="format">format string</param> <param name="args">the arguments</param> </member> </members> </doc> |