Merge pull request #12709 from Mikejo5000/mikejo-br24

Clarify TestSessionTimeout values for runsettings file and Docker values for remote test

Author: prmerger-automator[bot]

docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md

@@ -164,7 +164,7 @@ The **RunConfiguration** element can include the following elements:
 |**TreatTestAdapterErrorsAsWarnings**|false|false, true|
 |**TestAdaptersPaths**||One or more paths to the directory where the TestAdapters are located|
 |**TestCaseFilter**|| A filter expression in the format \<property>\<operator>\<value>[\|\&amp;\<Expression>]. The boolean operator **\&** should be represented by the HTML entity **\&amp;**. Expressions can be enclosed in parentheses. For detailed syntax on expression structure, see [vstest/docs/filter.md](https://github.com/microsoft/vstest/blob/main/docs/filter.md). |
-|**TestSessionTimeout**||Allows users to terminate a test session when it exceeds a given timeout. Setting a timeout ensures that resources are well consumed and test sessions are constrained to a set time. The setting is available in **Visual Studio 2017 version 15.5** and later.|
+|**TestSessionTimeout**||Allows users to terminate a test session when it exceeds a given timeout, specified in milliseconds. Setting a timeout ensures that resources are well consumed and test sessions are constrained to a set time. The setting is available in **Visual Studio 2017 version 15.5** and later.|
 |**DotnetHostPath**||Specify a custom path to dotnet host that is used to run the testhost. It's useful when you're building your own dotnet, for example when building the dotnet/runtime repository. Specifying this option skips looking for testhost.exe, and forces the use of testhost.dll.|
 |**TreatNoTestsAsError**|false| true or false <br>Specify a Boolean value, which defines the exit code when no tests are discovered. If the value is `true` and no tests are discovered, a nonzero exit code is returned. Otherwise, zero is returned.|
 

docs/test/remote-testing.md

@@ -78,16 +78,16 @@ For a Dockerfile, the environment can be specified in the *testEnvironments.json
 }
 ```
 
-The following example shows the *testenvironments.json* file for a local container image named `<mcr.microsoft.com/dotnet/core/sdk>`.
+The following example shows the *testenvironments.json* file for a local container image named `<mcr.microsoft.com/dotnet/sdk>`.
 
 ```json
 {
     "version": "1",
     "environments": [
         {
-            "name": "linux dotnet-core-sdk-3.1",
+            "name": "linux dotnet-sdk-5.0",
             "type": "docker",
-            "dockerImage": "mcr.microsoft.com/dotnet/core/sdk"
+            "dockerImage": "mcr.microsoft.com/dotnet/sdk"
         }
     ]
 }
@@ -96,7 +96,7 @@ The following example shows the *testenvironments.json* file for a local contain
 The following example shows a Dockerfile for running tests targeting .NET 5.0. The second line makes sure the debugger can connect and run in your container.
 
 ```dockerfile
-FROM mcr.microsoft.com/dotnet/core/sdk:5.0
+FROM mcr.microsoft.com/dotnet/sdk:5.0
 
 RUN wget https://aka.ms/getvsdbgsh && \
     sh getvsdbgsh -v latest  -l /vsdbg