Merge pull request #1589 from MicrosoftDocs/master

3/13 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -1802,6 +1802,11 @@
             "redirect_url": "/visualstudio/code-quality/code-analysis-for-managed-code-overview",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/test/analyzing-code-coverage-in-build-verification-tests.md",
+            "redirect_url": "/vsts/build-release/test/getting-started-with-continuous-testing",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/test/index.md",
             "redirect_url": "/visualstudio/test/improve-code-quality",

docs/debugger/using-breakpoints.md

@@ -60,7 +60,31 @@ You can set breakpoints when you want to stop debugger execution, perhaps to see
 
  You can set a breakpoint on any line of executable code. For example, in the C# code above you can set a breakpoint on the variable declaration, the `for` loop, or any code inside the `for` loop, but you cannot set a breakpoint on the namespace or class declarations or the method signature.  
 
-##  <a name="BKMK_Set_a_breakpoint_in_a_source_file"></a> Setting Other Kinds of Breakpoints  
+##  <a name="BKMK_Set_a_breakpoint_in_a_source_file"></a> Setting a function breakpoint  
+  You can break execution when a function is called.
+  
+1. Open the **Breakpoints** window and choose **New > Function Breakpoint**.
+
+2. Enter a function name in the **Function Name** box. 
+
+   To narrow the function specification:
+   
+   Use the fully qualified function name. 
+   Example:  Namespace1.ClassX.MethodA()
+   
+   Add the parameter types of an overloaded function. 
+   Example:  MethodA(int, string)
+   
+   Use the '!' symbol to specify the module.
+   Example: App1.dll!MethodA
+   
+   Use the context operator in native C++.
+   {function, , [module]} [+&lt;line offset from start of method&gt;]
+   Example: {MethodA, , App1.dll}+2
+
+3. In the **Language** dropdown, choose the specific language of the function you want to break on.
+  
+##  <a name="BKMK_Set_a_breakpoint_in_a_function"></a> Setting Other Kinds of Breakpoints  
  You can also set breakpoints in the call stack, in the Disassembly window, and, in native C++ code, at a data condition or a memory address.  
 
 ## <a name="BKMK_Set_a_breakpoint_in_the_call_stack_window"></a> Setting a Breakpoint in the Call Stack Window  

docs/docfx.json

@@ -48,7 +48,8 @@
       "ms.technology": "vs-ide-general",
       "ms.tgt_pltfrm": "dotnet",
       "searchScope": ["VS IDE"],
-      "uhfHeaderId": "MSDocsHeader-VisualStudio"
+      "uhfHeaderId": "MSDocsHeader-VisualStudio",
+      "titleSuffix": "Visual Studio"
     },
     "template": [],
     "xref": ["missingapi.yml", "../dotnet-xref/_zip/dotnet.zip"],

docs/test/TOC.md

@@ -50,7 +50,6 @@
 ### [Run unit tests for UWP apps](run-unit-tests-for-store-apps-in-visual-studio.md)
 ## [Use Code Coverage to Determine How Much Code is being Tested](using-code-coverage-to-determine-how-much-code-is-being-tested.md)
 ### [Customize Code Coverage Analysis](customizing-code-coverage-analysis.md)
-### [Analyze Code Coverage in Build Verification Tests](analyzing-code-coverage-in-build-verification-tests.md)
 ### [Troubleshoot Code Coverage](troubleshooting-code-coverage.md)
 ## [Use emulators to isolate unit tests for Sharepoint 2010 applications](using-emulators-to-isolate-unit-tests-for-sharepoint-2010-applications.md)
 # [Live Unit Testing](live-unit-testing-intro.md)

docs/test/analyzing-code-coverage-in-build-verification-tests.md

@@ -1,108 +1,108 @@
 ---
 title: "Analyzing Coded UI Tests Using Coded UI Test Logs | Microsoft Docs"
-ms.custom: ""
 ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
 ms.technology: vs-devops-test
-ms.tgt_pltfrm: ""
 ms.topic: "article"
 ms.author: gewarren
 manager: ghogen
-ms.workload: 
+ms.workload:
   - "multiple"
 author: gewarren
 ---
 # Analyzing Coded UI Tests Using Coded UI Test Logs
-Coded UI test logs filter and record important information about your coded UI test runs.  
-  
- **Requirements**  
-  
--   Visual Studio Enterprise  
-  
-## Why should I do this?  
- The logs are presented in a format that allows for debugging issues quickly.  
-  
-## How do I do this?  
-  
-### Step 1: Enable logging  
- Depending on your scenario, use one of the following methods to enable the log.  
-  
--   Target .NET Framework version 4 with no App.config file present in the test project  
-  
-    -   Open the **QTAgent32_40.exe.config** file.  
-  
-         By default, this file is located in **\<drvie>:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE**.  
-  
-         Modify the value for EqtTraceLevel to the log level you want.  
-  
-         Save the file.  
-  
--   Target .NET Framework version 4.5 with no App.config file present in the test project  
-  
-    -   Open the **QTAgent32.exe.config** file.  
-  
-         By default, this file is located in **\<drvie>:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE**.  
-  
-         Modify the value of the EqtTraceLevel to the log level you want.  
-  
-         Save the file.  
-  
--   App.config file present in the test project  
-  
-    -   Open App.config file in the project.  
-  
-         Add the following code under the configuration node:  
-  
-         `<system.diagnostics>     <switches>       <add name="EqtTraceLevel" value="4" />     </switches>  </system.diagnostics>`  
-  
--   Enable logging from the test code itself  
-  
-    -   <xref:Microsoft.VisualStudio.TestTools.UITesting.PlaybackSettings.LoggerOverrideState%2A> = HtmlLoggerState.AllActionSnapshot;  
-  
-### Step 2: Run your coded UI test and view the log  
- When you run a coded UI test with the modifications to the **QTAgent32.exe.config** file in place, you will see there is an output link in the Test Explorer results. Log files are produced not only when your test fails, but also for successful tests when the trace level is set to "verbose."  
-  
-1.  On the **TEST** menu, choose **Windows** and then select **Test Explorer**.  
-  
-2.  On the **BUILD** menu, choose **Build Solution**.  
-  
-3.  In Test Explorer, select the coded UI test you want to run, open its shortcut menu, and then choose **Run Select Tests**.  
-  
-     The automated tests will run and indicate if they passed or failed.  
-  
+
+Coded UI test logs filter and record important information about your coded UI test runs.
+
+ **Requirements**
+
+- Visual Studio Enterprise
+
+## Why should I do this?
+
+The logs are presented in a format that allows for debugging issues quickly.
+
+## How do I do this?
+
+### Step 1: Enable logging
+
+Depending on your scenario, use one of the following methods to enable the log.
+
+- Target .NET Framework version 4 with no App.config file present in the test project
+
+    - Open the **QTAgent32_40.exe.config** file.
+
+         By default, this file is located in **\<drvie>:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE**.
+
+         Modify the value for EqtTraceLevel to the log level you want.
+
+         Save the file.
+
+- Target .NET Framework version 4.5 with no App.config file present in the test project
+
+    - Open the **QTAgent32.exe.config** file.
+
+         By default, this file is located in **\<drvie>:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE**.
+
+         Modify the value of the EqtTraceLevel to the log level you want.
+
+         Save the file.
+
+- App.config file present in the test project
+
+    - Open App.config file in the project.
+
+         Add the following code under the configuration node:
+
+         `<system.diagnostics>     <switches>       <add name="EqtTraceLevel" value="4" />     </switches>  </system.diagnostics>`
+
+- Enable logging from the test code itself
+
+    - <xref:Microsoft.VisualStudio.TestTools.UITesting.PlaybackSettings.LoggerOverrideState%2A> = HtmlLoggerState.AllActionSnapshot;
+
+### Step 2: Run your coded UI test and view the log
+
+ When you run a coded UI test with the modifications to the **QTAgent32.exe.config** file in place, you see an output link in the Test Explorer results. Log files are produced not only when your test fails, but also for successful tests when the trace level is set to "verbose."
+
+1.  On the **TEST** menu, choose **Windows** and then select **Test Explorer**.
+
+2.  On the **BUILD** menu, choose **Build Solution**.
+
+3.  In Test Explorer, select the coded UI test you want to run, open its shortcut menu, and then choose **Run Select Tests**.
+
+     The automated tests run and indicate if they passed or failed.
+
     > [!TIP]
-    >  To view Test Explorer from the **Test menu**, point to **Windows** and then choose **Test Explorer**.  
-  
-4.  Choose the **Output** link in the Test Explorer results.  
-  
-     ![Output link in the Test Explorer](../test/media/cuit_htmlactionlog1.png "CUIT_HTMLActionLog1")  
-  
-     This displays the output for the test which will include a link to the action log.  
-  
-     ![Results and output links from coded UI test](../test/media/cuit_htmlactionlog2.png "CUIT_HTMLActionLog2")  
-  
-5.  Choose the UITestActionLog.html link.  
-  
-     The log is displayed in your web browser.  
-  
-     ![Coded UI test log file](../test/media/cuit_htmlactionlog3.png "CUIT_HTMLActionLog3")  
-  
-## Q & A  
-  
-### Q: What happened to the EnableHtmlLogger key?  
- In previous versions of Visual Studio, there were two more configuration settings for enabling Html Logger in Coded UI Test:  
-  
-```  
-  
-<add key="EnableHtmlLogger" value="true"/>  
-  
-<add key="EnableSnapshotInfo" value="true"/>  
-  
-```  
-  
- Both of these settings have been deprecated since Visual Studio 2012. EqtTraceLevel is the only setting which is required to be modified to enable HtmlLogger.  
-  
-## See Also  
- [Use UI Automation To Test Your Code](../test/use-ui-automation-to-test-your-code.md)   
- [How to: Run Tests from Microsoft Visual Studio](http://msdn.microsoft.com/Library/1a1207a9-2a33-4a1e-a1e3-ddf0181b1046)
+    >  To view Test Explorer from the **Test menu**, point to **Windows** and then choose **Test Explorer**.
+
+4.  Choose the **Output** link in the Test Explorer results.
+
+     ![Output link in the Test Explorer](../test/media/cuit_htmlactionlog1.png "CUIT_HTMLActionLog1")
+
+     This displays the output for the test, which includes a link to the action log.
+
+     ![Results and output links from coded UI test](../test/media/cuit_htmlactionlog2.png "CUIT_HTMLActionLog2")
+
+5.  Choose the *UITestActionLog.html* link.
+
+     The log is displayed in your web browser.
+
+     ![Coded UI test log file](../test/media/cuit_htmlactionlog3.png "CUIT_HTMLActionLog3")
+
+## Q & A
+
+### Q: What happened to the EnableHtmlLogger key?
+
+In previous versions of Visual Studio, there were two more configuration settings for enabling Html Logger in Coded UI Test:
+
+```xml
+<add key="EnableHtmlLogger" value="true"/>
+
+<add key="EnableSnapshotInfo" value="true"/>
+```
+
+Both of these settings have been deprecated since Visual Studio 2012. EqtTraceLevel is the only setting that is required to be modified to enable HtmlLogger.
+
+## See also
+
+- [Use UI Automation To Test Your Code](../test/use-ui-automation-to-test-your-code.md)
+- [How to: Run Tests from Microsoft Visual Studio](http://msdn.microsoft.com/Library/1a1207a9-2a33-4a1e-a1e3-ddf0181b1046)