Update: the usage instructions for parameter <ConsiderFixturesAsSpeci…

…alTests> (#42567) * Update unit-testing-mstest-configure.md Add description for ConsiderFixturesAsSpecialTests * Update unit-testing-mstest-configure.md Fix comments * Update docs/core/testing/unit-testing-mstest-configure.md --------- Co-authored-by: David Pine <[email protected]>
dotnet · Sep 11, 2024 · 495b9fb · 495b9fb
1 parent dfb612d
commit 495b9fb
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/docs/core/testing/unit-testing-mstest-configure.md b/docs/core/testing/unit-testing-mstest-configure.md
@@ -43,6 +43,7 @@ The following runsettings entries let you configure how MSTest behaves.
 |**TestTimeout**|0|Gets specified global test case timeout.|
 |**TreatClassAndAssemblyCleanupWarningsAsErrors**|false|To see your failures in class cleanups as errors, set this value to **true**.|
 |**TreatDiscoveryWarningsAsErrors**|false|To report test discovery warnings as errors, set this value to **true**.|
+|**ConsiderFixturesAsSpecialTests**|false|To display `AssemblyInitialize`, `AssemblyCleanup`, `ClassInitialize`, `ClassCleanup` as individual entries in Visual Studio and Visual Studio Code `Test Explorer` and _.trx_ log, set this value to **true**|
 
 ### `TestRunParameter` element
 
@@ -90,6 +91,7 @@ Each element of the file is optional because it has a default value.
     <CaptureTraceOutput>false</CaptureTraceOutput>
     <DeleteDeploymentDirectoryAfterTestRunIsComplete>False</DeleteDeploymentDirectoryAfterTestRunIsComplete>
     <DeploymentEnabled>False</DeploymentEnabled>
+    <ConsiderFixturesAsSpecialTests>False</ConsiderFixturesAsSpecialTests>
     <AssemblyResolution>
       <Directory path="D:\myfolder\bin\" includeSubDirectories="false"/>
     </AssemblyResolution>