Skip to content

Update: the usage instructions for parameter <ConsiderFixturesAsSpecialTests> #10391

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Sep 11, 2024
Merged

Update: the usage instructions for parameter <ConsiderFixturesAsSpecialTests> #10391

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
8bed605
Update configure-unit-tests-by-using-a-dot-runsettings-file.md
wenbo97 Sep 10, 2024
516ca6e
Merge pull request #1 from Vincezhaoc/vince-patch1
wenbo97 Sep 10, 2024
57a6d00
Update configure-unit-tests-by-using-a-dot-runsettings-file.md
wenbo97 Sep 10, 2024
6111f6b
Merge pull request #2 from Vincezhaoc/Vincezhaoc-patch-2
wenbo97 Sep 10, 2024
5e94027
Update configure-unit-tests-by-using-a-dot-runsettings-file.md
wenbo97 Sep 10, 2024
d39cadd
Merge branch 'MicrosoftDocs:main' into main
wenbo97 Sep 11, 2024
c56e932
Update configure-unit-tests-by-using-a-dot-runsettings-file.md
wenbo97 Sep 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -308,6 +308,7 @@ These settings are specific to the test adapter that runs test methods that have
<CaptureTraceOutput>false</CaptureTraceOutput>
<DeleteDeploymentDirectoryAfterTestRunIsComplete>False</DeleteDeploymentDirectoryAfterTestRunIsComplete>
<DeploymentEnabled>False</DeploymentEnabled>
<ConsiderFixturesAsSpecialTests>False</ConsiderFixturesAsSpecialTests>
<AssemblyResolution>
<Directory path="D:\myfolder\bin\" includeSubDirectories="false"/>
</AssemblyResolution>
Expand All @@ -330,6 +331,7 @@ These settings are specific to the test adapter that runs test methods that have
|**DeployTestSourceDependencies**|true|A value indicating whether the test source references are to be deployed.|
|**DeleteDeploymentDirectoryAfterTestRunIsComplete**|true|To retain the deployment directory after a test run, set this value to **false**.|
|**MapInconclusiveToFailed**|false|If a test completes with an inconclusive status, it's mapped to the skipped status in **Test Explorer**. If you want inconclusive tests to be shown as failed, set the 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**|
|**AssemblyResolution**|false|You can specify paths to extra assemblies when finding and running unit tests. For example, use these paths for dependency assemblies that aren't in the same directory as the test assembly. To specify a path, use a **Directory Path** element. Paths can include environment variables.<br /><br />`<AssemblyResolution> <Directory path="D:\myfolder\bin\" includeSubDirectories="false"/> </AssemblyResolution>`<br /><br />Note that this feature is only being applied when using .NET Framework target.|

## Example *.runsettings* file
Expand Down