From 47ef27e74e3cdf9568ad1edc3d27dffeff93066f Mon Sep 17 00:00:00 2001 From: fuguikz <2514883828@qq.com> Date: Wed, 25 Feb 2026 18:11:42 +0800 Subject: [PATCH] docs(vstest): update TestAdapter version --- docs/articles/features/vstest.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/articles/features/vstest.md b/docs/articles/features/vstest.md index 9163cb43e5..4d5d5fdf20 100644 --- a/docs/articles/features/vstest.md +++ b/docs/articles/features/vstest.md @@ -73,7 +73,7 @@ In addition, we can still make use of this boolean output to indicate - + @@ -82,12 +82,12 @@ In addition, we can still make use of this boolean output to indicate * **Step 3.** Make sure that your IDE supports VSTest integration. In Visual Studio, everything works out of the box. - In Rider/R# 2023.3, the VSTest integration should be activated: + In Rider/R#, the VSTest integration might need to be activated: * Go to the "Unit Testing" settings page. * Rider: Settings -> Build, Execution, Deployment -> Unit Testing -> VSTest * R#: Extensions -> ReSharper -> Options -> Tools -> Unit Testing -> Test Frameworks -> VSTest * Make sure that the "Enable VSTest adapter support" checkbox is checked. - In future versions of Rider, this should be enabled by default. + In recent versions of Rider, this may be enabled by default. * **Step 4.** Switch to the `Release` configuration. As mentioned above, the TestAdapter is not able to discover and run benchmarks with optimizations disabled (by design). * **Step 5.** Build the project.