Merge pull request #2255 from craigcaseyMSFT/vcraic0629-3

More CATS fixes for test folder

Author: TrishaMc

docs/test/counters-panel-in-load-test-analyzer.md

@@ -41,7 +41,7 @@ The Counters panel provides the following features:
 
 ### Scenario Name Node in Counters Panel
 
-|||
+|Counters Panel|Description|
 |-|-|
 |![Counter panel's scenario name node](../test/media/ltest__namenode.png)|1. All performance counters associated with Scenario1 of the load test appear under this node.<br />2. All tests of a scenario are located beneath the scenario node. The label indicates the test name.<br />3. Leaf nodes under a test node are load test test case counters, where the instance name for the counter is the test name.<br />4. All load test page counter instances associated with a Web performance test branch. At this node, all the load test pace counter instances associated with page Login GET (Reporting name) of the IBuyBrowse Web performance test in Scenario1 of the load test are contained here.<br />5. Leaf nodes under a page node are load test page counters.<br />6. All load test requests counter instances associated with a Web performance test are contained within a Web performance test branch. At this node, all request counter instances associated with the request Login GET (Reporting name) of IBuyBrowse Web performance test in Scenario1 o the load test contained here.<br />7. Leaf nodes under a request node are load test request counters.<br />8. All load test transaction counter instances associated with a Web performance test are contained within a Web performance test branch. At this node, all transaction counter instances associate with the transaction named Transaction1 of the IBuyBrowse Web performance test in Scenraio1 of the load test are contained here.<br />9. Leaf nodes under a transaction node are load test transaction counters.<br />10. Unit test node.|
 

docs/test/edit-load-test-scenarios.md

@@ -27,9 +27,8 @@ Any initial configuration options and settings that you specify when you create
 
 Scenarios contain the following components:
 
-|||
-|-|-|
 |Term|Definition|
+|-|-|
 |Browser Mix|Simulates that virtual users access a Web site through a variety of Web browsers.|
 |Load Pattern|Specifies the number of virtual users that are active during a load test, and the rate at which new users are started. For example: step, constant, and goal-based.|
 |Test Mix Model|Specifies the probability of a virtual user running a given test in a load test scenario. For example: 20% chance to run TestA and 80% chance to run TestB. The test mix model should reflect the objectives of your test for a particular scenario.|

docs/test/how-to-view-web-page-response-time-in-a-load-test.md

@@ -39,7 +39,7 @@ If you run your Web performance test under stress in a load test, you will be ab
 
 3.  The data for each page is displayed in the grid. The following columns are ordinarily displayed.
 
-    |||
+    |Column Heading|Description|
     |-|-|
     |**Page**|The name of the Web page.|
     |**Scenario**|The name of the scenario. Important if you have more than one scenario in your Web performance test.|

docs/test/how-to-write-unit-tests-for-cpp-dlls.md

@@ -108,7 +108,7 @@ author: mikeblome
 
     3.  Edit the Include and Library directories:
 
-        |||
+        |Directory|Property|
         |-|-|
         |**Include Directories** | **$(VCInstallDir)UnitTest\include;$(IncludePath)**|
         |**Library Directories** | **$(VCInstallDir)UnitTest\lib;$(LibraryPath)**|

docs/test/live-unit-testing.md

@@ -52,7 +52,7 @@ If you have older MSTest based test projects that are referencing `Microsoft.Vis
 
 In some cases, you may need to explicitly restore the NuGet packages referenced by the projects in the solution in order for Live Unit Testing to work. You can do this either by doing an explicit build of the solution (select **Build**, **Rebuild Solution** from the top-level Visual Studio menu) or by restoring packages in the solution (right-click on the solution and select **Restore NuGet Packages**) before enabling Living Unit Testing. 
 
-#	Configuring Live Unit Testing
+## Configuring Live Unit Testing
 
 You can configure Live Unit Testing by selecting **Tools**, **Options** from the top-level Visual Studio menu, and then selecting **Live Unit Testing** in the left pane of the **Options** dialog. The following figure shows the Live Unit Testing configuration options available in the dialog.
 

docs/test/run-unit-tests-with-test-explorer.md

@@ -48,7 +48,7 @@ The pass/fail bar at the top of the Test Explorer window is animated as the test
 
 ### Run tests after every build
 
-|||
+|Button|Description|
 |-|-|
 |![Run after build](../test/media/ute_runafterbuild_btn.png)|To run your unit tests after each local build, choose **Test** on the standard menu, and then choose **Run Tests After Build** on the Test Explorer toolbar.|
 
@@ -148,7 +148,7 @@ To filter by a different criteria:
 
 To exclude a subset of the results of a filter, use the following syntax:
 
-```
+```cpp
 FilterName:"Criteria" -FilterName:"SubsetCriteria"
 ```
 

docs/test/unit-test-basics.md

@@ -90,7 +90,7 @@ It is often quicker to generate the unit test project and unit test stubs from y
 
      ![The unit tests are created](../test/media/createunittestsstubs.png)
 
-4.  Now jump ahead to learn how to [add code to the unit test methods](#BKMK_Writing_your_tests) to make your unit test meaningful, and any extra unit tests that you might want to add to thoroughly test your code.
+4.  Now jump ahead to learn how to [add code to the unit test methods](#write-your-tests) to make your unit test meaningful, and any extra unit tests that you might want to add to thoroughly test your code.
 
  **Create your unit test project and unit tests manually**
 
@@ -220,7 +220,7 @@ The Test Explorer toolbar helps you discover, organize, and run the tests that y
 > [!WARNING]
 > Running unit tests after every build is supported only in Visual Studio Enterprise.
 
-|||
+|Button|Description|
 |-|-|
 |![Run after build](../test/media/ute_runafterbuild_btn.png)|To run your unit tests after each local build, choose **Test** on the standard menu, choose **Run Tests After Build** on the Test Explorer toolbar.|
 
@@ -230,7 +230,7 @@ When you have a large number of tests, you can Type in Test Explorer search box
 
  ![Search filter categories](../test/media/ute_searchfilter.png)
 
-|||
+|Button|Description|
 |-|-|
 |![Test Explorer group button](../test/media/ute_groupby_btn.png)|To group your tests by category, choose the **Group By** button.|
 

docs/test/using-html5-controls-in-coded-ui-tests.md

@@ -26,18 +26,7 @@ Coded UI tests include support for some of the HTML5 controls that are included
 > If you create a coded UI test in Internet Explorer 10, it might not run using Internet Explorer 9 or Internet Explorer 8. This is because Internet Explorer 10 includes HTML5 controls such as Audio, Video, ProgressBar and Slider. These HTML5 controls are not recognized by Internet Explorer 9, or Internet Explorer 8. Likewise, your coded UI test using Internet Explorer 9 might include some HTML5 controls that also will not be recognized by Internet Explorer 8.
 
 
-## Supported HTML5 Controls
- Coded UI tests include support for record, playback, and validation of the following HTML5 controls:
-
--   [Audio Control](#UsingHTML5ControlsCodedUITestsAudio)
-
--   [Video Control](#UsingHTML5ControlsCodedUITestsVideo)
-
--   [Slider](#UsingHTML5ControlsCodedUITestsSlider)
-
--   [ProgressBar](#UsingHTML5ControlsCodedUITestsProgressBar)
-
-###  <a name="UsingHTML5ControlsCodedUITestsAudio"></a> Audio Control
+## Audio Control
  **Audio control:** Actions on the HTML5 Audio control are correctly recorded and played back.
 
  ![HTML5 Audio control](../test/media/codedui_html5_audio.png)
@@ -51,27 +40,7 @@ Coded UI tests include support for some of the HTML5 controls that are included
 |**Unmute audio**<br /><br /> Directly from control, or from controls context menu.|Unmute \<name> Audio|HtmlAudio.Unmute()|
 |**Change volume of audio**|Set volume of \<name> Audio to 79%|HtmlAudio.SetVolume(float)|
 
- The following properties are available for HtmlAudio and you can add an assertion on all of them:
-
-```
-string AutoPlay
-string Controls
-string CurrentSrc
-string CurrentTime
-string CurrentTimeAsString
-string Duration
-string DurationAsString
-string Ended
-string Loop
-string Muted
-string Paused
-string PlaybackRate
-string ReadyState
-string Seeking
-string Src
-string Volume
-
-```
+See [HTMLAudioElement](https://developer.mozilla.org/docs/Web/API/HTMLAudioElement) for a list of properties on which you can add an assertion.
 
  **Search properties:** The search properties for `HtmlAudio` are `Id`, `Name` and `Title`.
 
@@ -81,7 +50,7 @@ string Volume
 > The amount of time for Seek and Pause can be significant. During playback, the coded UI test will wait until the specified time in `(TimeSpan)` before Pausing the audio. If by some special circumstance, the specified time has passed before hitting the Pause command, an exception will be thrown.
 
 
-###  <a name="UsingHTML5ControlsCodedUITestsVideo"></a> Video Control
+## Video Control
  **Video control:** Actions on the HTML5 Video control are correctly recorded and played back.
 
  ![HTML5 Video control](../test/media/codedui_html5_video.png)
@@ -95,14 +64,7 @@ string Volume
 |**Unmute video**<br /><br /> Directly from control, or from controls context menu.|Unmute \<name> Video|HtmlVideo.Unmute()|
 |**Change volume of video**|Set volume of \<name> Video to 79%||
 
- All the properties of HtmlAudio are available for HtmlVideo. In addition, the following three properties are also available. Assertion can be added on all of them.
-
-```
-string Poster
-string VideoHeight
-string VideoWidth
-
-```
+See [HTMLVideoElement](https://developer.mozilla.org/docs/Web/HTML/Element/video) for a list of properties on which you can add an assertion.
 
  **Search properties:** The search properties for `HtmlVideo` are `Id`, `Name` and `Title`.
 
@@ -111,35 +73,14 @@ string VideoWidth
 > [!NOTE]
 > If you rewind or fast forward the video using -30s or +30s labels, this will be aggregated to seek to the appropriate time.
 
-
-###  <a name="UsingHTML5ControlsCodedUITestsSlider"></a> Slider
- **Slider control:** Actions on the HTML5 Slider control are correctly recorded and played back.
-
- ![HTML5 Slider control](../test/media/codedui_html5_slider.png)
-
-|Action|Recording|Generated Code|
-|------------|---------------|--------------------|
-|**Set a position in the slider**|Set position to \<x> in \<name> slider|HtmlSlider.ValueAsNumber=\<x>|
-
- The following properties are available for HtmlSlider and assertion can be added on all of them:
-
-```
-string Disabled
-string Max
-string Min
-string Required
-string Step
-string ValueAsNumber
-```
-
-###  <a name="UsingHTML5ControlsCodedUITestsProgressbar"></a> ProgressBar
- **ProgreesBar control:** The ProgressBar is a non-interactable control. You can add assertions on the `Value` and `Max` properties of this control.
+## ProgressBar
+ **ProgressBar control:** The ProgressBar is a non-interactable control. You can add assertions on the `Value` and `Max` properties of this control. For more information, see [HTMLProgressElement](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/progress).
 
  ![HTML5 ProgressBar control](../test/media/codedui_html5_progressbar.png)
 
 ## See also
 
-- [HTML Elements](http://go.microsoft.com/fwlink/?LinkID=232441)
+- [HTML Elements](https://developer.mozilla.org/docs/Web/HTML/Element)
 - [Use UI Automation To Test Your Code](../test/use-ui-automation-to-test-your-code.md)
 - [Creating Coded UI Tests](../test/use-ui-automation-to-test-your-code.md)
 - [Supported Configurations and Platforms for Coded UI Tests and Action Recordings](../test/supported-configurations-and-platforms-for-coded-ui-tests-and-action-recordings.md)

docs/test/walkthrough-using-a-configuration-file-to-define-a-data-source.md

@@ -62,7 +62,7 @@ Examine the *app.config* file. It contains at least the XML declaration and a ro
 
 The **section** element should look similar to this:
 
-```
+```xml
 <section name="microsoft.visualstudio.testtools" type="Microsoft.VisualStudio.TestTools.UnitTesting.TestConfigurationSection, Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
 ```
 
@@ -89,15 +89,15 @@ The connection strings define provider-specific information for accessing data s
 
 In the second **add** element, create the following attributes and values for a connection to a Microsoft Excel spreadsheet:
 
-|||
+|Attribute|Values|
 |-|-|
 |`name`|`"MyExcelConn"`|
 |`connectionString`|`"Dsn=Excel Files;dbq=data.xlsx;defaultdir=.\; driverid=790;maxbuffersize=2048;pagetimeout=5"`|
 |`providerName`|`"System.Data.Odbc"`|
 
 The **connectionStrings** element should look similar to this:
 
-```
+```xml
 <connectionStrings>
     <add name="MyJetConn" connectionString="Provider=Microsoft.Jet.OLEDB.4.0; Data Source=C:\testdatasource.accdb; Persist Security Info=False;" providerName="System.Data.OleDb" />
     <add name="MyExcelConn" connectionString="Dsn=Excel Files;dbq=data.xlsx;defaultdir=.\; driverid=790;maxbuffersize=2048;pagetimeout=5" providerName="System.Data.Odbc" />
@@ -137,7 +137,7 @@ In this section, you'll define two data sources to use in a unit test.
 
 In the second **add** element, create the following attributes and values for a Microsoft Excel data source:
 
-|||
+|Attribute|Values|
 |-|-|
 |`Name`|`"MyExcelDataSource"`|
 |`connectionString`|`"MyExcelConn"`|

docs/test/walkthrough-writing-unit-tests-for-cpp-dlls.md

@@ -296,7 +296,7 @@ This walkthrough describes how to develop a native C++ DLL using test-first meth
 
 1.  Simplify the central calculation in the SquareRoot function:
 
-    ```
+    ```cpp
     // old code:
     //   result = result - (result*result - v)/(2*result);
     // new code:
@@ -324,7 +324,7 @@ This walkthrough describes how to develop a native C++ DLL using test-first meth
 ## See also
 
 - [Adding unit tests to existing C++ applications](../test/unit-testing-existing-cpp-applications-with-test-explorer.md)
-- [Using Microsoft.VisualStudio.TestTools.CppUnitTestFramework](../test/using-microsoft-visualstudio-testtools-cppunittestframework.md)
+- [Using Microsoft.VisualStudio.TestTools.CppUnitTestFramework](how-to-use-microsoft-test-framework-for-cpp.md)
 - [Debugging Native Code](../debugger/debugging-native-code.md)
 - [Walkthrough: Creating and Using a Dynamic Link Library (C++)](/cpp/build/walkthrough-creating-and-using-a-dynamic-link-library-cpp)
 - [Importing and Exporting](/cpp/build/importing-and-exporting)