Merge pull request #2531 from craigcaseyMSFT/vcraic0718

Content update project in test folder (41-50)

Author: ktoliver

docs/test/extending-coded-ui-tests-and-action-recordings-to-support-microsoft-excel.md

@@ -10,7 +10,7 @@ ms.workload:
   - "multiple"
 author: gewarren
 ---
-# Extend Coded UI Tests and Action Recordings
+# Extend coded UI tests and action recordings
 
 The testing framework for coded UI tests and action recordings does not support every possible user interface. It might not support the specific UI that you want to test. For example, you cannot immediately create a coded UI test or an action recording for a Microsoft Excel spreadsheet. However, you can create your own extension to the coded UI test framework that supports your specific UI by taking advantage of the extensibility of the coded UI test framework.
 
@@ -29,6 +29,6 @@ This [blog post](https://blogs.msdn.microsoft.com/gautamg/2010/01/05/3-introduci
 - <xref:Microsoft.VisualStudio.TestTools.UITest.Extension.UITechnologyElement>
 - <xref:Microsoft.VisualStudio.TestTools.UITest.Common.UITestActionFilter>
 - <xref:Microsoft.VisualStudio.TestTools.UITest.Extension.UITestExtensionPackage>
-- [Use UI Automation To Test Your Code](../test/use-ui-automation-to-test-your-code.md)
-- [Best Practices for Coded UI Tests](../test/best-practices-for-coded-ui-tests.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)
+- [Use UI automation to test your code](../test/use-ui-automation-to-test-your-code.md)
+- [Best practices for coded UI tests](../test/best-practices-for-coded-ui-tests.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/fix-non-detectable-dynamic-parameters-in-a-web-performance-test.md

@@ -29,11 +29,11 @@ Some types of dynamic parameters are not detected. An undetected dynamic paramet
 
 To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll create a simple ASP.NET web application that has three web forms with a few controls and some custom code. We’ll then learn how to isolate the dynamic parameters and how to handle them.
 
-1.  Create a new ASP.NET project named DynamicParamaterSample.
+1.  Create a new ASP.NET project named **DynamicParameterSample**.
 
      ![Create an empty ASP.NET web application project](../test/media/web_test_dynamicparameter_aspproject.png)
 
-2.  Add a web form named Querystring.aspx.
+2.  Add a web form named *Querystring.aspx*.
 
 3.  In design view, drag a HiddenField onto the page and in then in change the value for the (ID) property to HiddenFieldSessionID.
 
@@ -56,7 +56,7 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
     </html>
     ```
 
-5.  Open the Querystring.aspx.cs file and add the following highlighted code to the Page_Load method:
+5.  Open the *Querystring.aspx.cs* file and add the following highlighted code to the Page_Load method:
 
     ```csharp
     public partial class Querystring : System.Web.UI.Page
@@ -68,25 +68,25 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
     }
     ```
 
-6.  Add a second web form named ASPQuery.aspx.
+6.  Add a second web form named *ASPQuery.aspx*.
 
-7.  In design view, drag a Label onto the page and change the value for its (ID) property to IndexLabel.
+7.  In design view, drag a **Label** onto the page and change the value for its **(ID)** property to **IndexLabel**.
 
      ![Add a label to the web form](../test/media/web_test_dynamicparameter_label.png)
 
-8.  Drag a HyperLink onto the page and change the vale for its Text property to Back.
+8.  Drag a **HyperLink** onto the page and change the vale for its **Text** property to **Back**.
 
      ![Add a hyperlink to the web form](../test/media/web_test_dynamicparameter_hyperlink.png)
 
-9. Choose (…) for the NavigationURL property.
+9. Choose **(…)** for the **NavigationURL** property.
 
      ![Edit the NavigateURL property](../test/media/web_test_dynamicparameter_hyperlink_navurl.png)
 
-     Select Querystring.aspx.
+     Select *Querystring.aspx*.
 
      ![Choose the URL to be Querystring.aspx](../test/media/web_test_dynamicparameter_hyperlink_navurl2.png)
 
-10. Open the ASPQuery.aspx.cs file, and add the following highlighted code to the Page_Load method:
+10. Open the *ASPQuery.aspx.cs* file, and add the following highlighted code to the Page_Load method:
 
     ```csharp
     protected void Page_Load(object sender, EventArgs e)
@@ -95,13 +95,13 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
             }
     ```
 
-11. Add a third web form named JScriptQuery.aspx.
+11. Add a third web form named *JScriptQuery.aspx*.
 
-     Just as we did for the second page, drag a label onto the form, setting its (ID) property to IndexLabel and drag a Hyperlink onto the form, setting its text property to Back, and its NavigationURL property to Querystring.aspx.
+     Just as we did for the second page, drag a **Label** onto the form, setting its **(ID)** property to **IndexLabel** and drag a **Hyperlink** onto the form, setting its **Text** property to **Back**, and its **NavigationURL** property to **Querystring.aspx**.
 
      ![Add and configure the third web form](../test/media/web_test_dynamicparameter_addwebform3.png)
 
-12. Open the JScriptQuery.aspx.cs file, and add the following highlighted code to the Page_Load method:
+12. Open the *JScriptQuery.aspx.cs* file, and add the following highlighted code to the Page_Load method:
 
     ```csharp
     protected void Page_Load(object sender, EventArgs e)
@@ -112,11 +112,11 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
 
 13. Save the project.
 
-14. In Solution Explorer, set the Querystring.aspx as the start page.
+14. In **Solution Explorer**, set the *Querystring.aspx* as the start page.
 
      ![Set the start page on Querystring.aspx](../test/media/web_test_dynamicparameter_setstartpage.png)
 
-15. Press CTRL+F5 to run the web application in the browser. Copy the URL. You will need it when you record your test.
+15. Press **Ctrl**+**F5** to run the web application in the browser. Copy the URL. You will need it when you record your test.
 
 16. Try both links. They should each display the message "Success. Dynamic querystring parameter found."
 
@@ -146,21 +146,21 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
 
      The web test recorder displays the HTTP request and response URLs as you navigate through the web app.
 
-6.  Choose the stop button on the test recorder.
+6.  Choose the **Stop** button on the test recorder.
 
      The dialog box for detecting dynamic parameters displays a progress bar that shows the status of parameter detection in the HTTP responses that were received.
 
 7.  The dynamic parameter for CustomQueryString in the ASPQuery page is automatically detected. However, The dynamic parameter for CustomQueryString in the JScriptQuery page is not detected.
 
-     Choose OK to add an extraction rule to Querystring.aspx, binding it to the ASPQuery page.
+     Choose **OK** to add an extraction rule to *Querystring.aspx*, binding it to the ASPQuery page.
 
      ![Promote the detected dynamic parameter](../test/media/web_test_dynamicparameter_promotedialog.png)
 
-     The extraction rule is added to the first request for Querystring.aspx.
+     The extraction rule is added to the first request for *Querystring.aspx*.
 
      ![Extraction rule added to request](../test/media/web_test_dynamicparameter_autoextractionrule.png)
 
-     Expand the second request in the request tree for ASPQuery.aspx and notice that the CustomQueryString's value has been bound to the extraction rule.
+     Expand the second request in the request tree for *ASPQuery.aspx* and notice that the CustomQueryString's value has been bound to the extraction rule.
 
      ![CustomQueryString bound to extraction rule](../test/media/web_test_dynamicparameter_autoextractionrule2.png)
 
@@ -172,21 +172,21 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
 
      ![Run the web performance test](../test/media/web_test_dynamicparameter_runtest.png)
 
-2.  The fourth request for the JScriptQuery.aspx page fails. Go to the web test.
+2.  The fourth request for the *JScriptQuery.aspx* page fails. Go to the web test.
 
      ![Dynamic parameter error in test results](../test/media/web_test_dynamicparameter_runresults.png)
 
-     The JScriptQuery.aspx request node is highlighted in the editor. Expand the node and notice that the "1v0yhyiyr0raa2w4j4pwf5zl" portion of the CustomQueryString appears to be dynamic.
+     The *JScriptQuery.aspx* request node is highlighted in the editor. Expand the node and notice that the "1v0yhyiyr0raa2w4j4pwf5zl" portion of the CustomQueryString appears to be dynamic.
 
      ![Suspected dynamic parameter in CustomQueryString](../test/media/web_test_dynamicparameter_runresults2.png)
 
-3.  Return to the Web Performance Test Results Viewer and select the JScriptQuery.aspx page that failed. Then, choose the request tab, verify that the show raw data check box is cleared, scroll down and choose quick find on the CustomQueryString.
+3.  Return to the Web Performance Test Results Viewer and select the *JScriptQuery.aspx* page that failed. Then, choose the request tab, verify that the show raw data check box is cleared, scroll down and choose quick find on the CustomQueryString.
 
      ![Use quick find to isolate the dynamic paramter](../test/media/web_test_dynamicparameter_runresultsquckfind.png)
 
-4.  We know from looking at the test editor, that the JScriptQuery.aspx request's CustomQueryString was assigned a value of: `jScriptQueryString___1v0yhyiyr0raa2w4j4pwf5zl`, and that the suspected dynamic portion is "1v0yhyiyr0raa2w4j4pwf5zl". In the find what drop-down list, remove the suspect portion of the search string. The string should be "CustomQueryString=jScriptQueryString___".
+4.  We know from looking at the test editor, that the *JScriptQuery.aspx* request's CustomQueryString was assigned a value of: `jScriptQueryString___1v0yhyiyr0raa2w4j4pwf5zl`, and that the suspected dynamic portion is "1v0yhyiyr0raa2w4j4pwf5zl". In the find what drop-down list, remove the suspect portion of the search string. The string should be "CustomQueryString=jScriptQueryString___".
 
-     Dynamic parameters are assigned their values in one of the requests that precedes the request that has the error. Therefore, select the search up check box and choose find next until you see preceding request for Querystring.aspx highlighted in the request panel. This should occur after you choose find next three times.
+     Dynamic parameters are assigned their values in one of the requests that precedes the request that has the error. Therefore, select the search up check box and choose find next until you see preceding request for *Querystring.aspx* highlighted in the request panel. This should occur after you choose find next three times.
 
      ![Use quick find to isolate the dynamic parameter](../test/media/web_test_dynamicparameter_runresultsquckfind4.png)
 
@@ -209,33 +209,33 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
 
      ![Choose recorded result](../test/media/web_test_dynamicparameter_recordedresult.png)
 
-7.  In the recorded results, select the third request, which is the same Querystringrequest.aspx request that you isolated in the test run results.
+7.  In the recorded results, select the third request, which is the same *Querystringrequest.aspx* request that you isolated in the test run results.
 
      ![Choose the same request in the recorded results](../test/media/web_test_dynamicparameter_recordedresultsselectnode.png)
 
      Choose the response tab, scroll down and choose the original dynamic parameter value of "1v0yhyiyr0raa2w4j4pwf5zl" that you isolated previously and add an extraction rule.
 
      ![Add an extraction rule for the dynamic parameter](../test/media/web_test_dynamicparameter_recordedresultaddextractionrule.png)
 
-     The new extraction rule is added to the Querystring.aspx request and is assigned a value of 'Param0'.
+     The new extraction rule is added to the *Querystring.aspx* request and is assigned a value of 'Param0'.
 
-     If the dialog box informs us that matches were found for the extracted text to bind the parameter to, choose yes.
+     If the dialog box informs us that matches were found for the extracted text to bind the parameter to, choose **Yes**.
 
      ![Extraction rule created](../test/media/web_test_dynamicparameter_addextractiondialog.png)
 
-8.  Choose find next. The first match is the one that we need to change, which is the parameter for CustomQueryString in for the JScriptQuery page.
+8.  Choose **Find Next**. The first match is the one that we need to change, which is the parameter for CustomQueryString in for the JScriptQuery page.
 
      ![Find and replace the text for the parameter](../test/media/web_test_dynamicparameter_addextractionfindreplace.png)
 
-9. Choose replace.
+9. Choose **Replace**.
 
      ![Replace the text with the parameter](../test/media/web_test_dynamicparameter_addextractionfindreplace2.png)
 
-     The QueryString parameter under the JScriptQuery.aspx request is updated by using the new context parameter:  CustomQueryString=jScriptQueryString___{{Param0}}.
+     The QueryString parameter under the *JScriptQuery.aspx* request is updated by using the new context parameter:  CustomQueryString=jScriptQueryString___{{Param0}}.
 
      ![Parameter applied to querystring](../test/media/web_test_dynamicparameter_addextractionfindreplace3.png)
 
-10. Close the find and replace dialog. Notice the similar structure of in the request tree between the detected dynamic parameter and the non-detected dynamic parameter that you correlated.
+10. Close the **Find and Replace** dialog. Notice the similar structure of in the request tree between the detected dynamic parameter and the non-detected dynamic parameter that you correlated.
 
      ![Detected and correlated dynamic parameters](../test/media/web_test_dynamicparameter_conclusion.png)
 
@@ -247,13 +247,13 @@ To demonstrate both a detectable and a non-detectable dynamic parameter, we’ll
 
  **A:** Yes, use the following procedure:
 
-1.  In the toolbar, choose the Promote Dynamic Parameters to Web Test Parameters button.
+1.  In the toolbar, choose the **Promote Dynamic Parameters to Web Test Parameters** button.
 
-     After the detection process completes, if any dynamic parameters are detected, the Promote Dynamic Parameters to web test parameters dialog box appears.
+     After the detection process completes, if any dynamic parameters are detected, the **Promote Dynamic Parameters to web test parameters** dialog box appears.
 
      The dynamic parameters are listed under the Dynamic Parameters column. The requests that the dynamic parameter will be extracted from and bound to are listed under the Extract Parameter from Response and Bind to Request columns.
 
-     If you choose a dynamic parameter in the Promote Dynamic Parameters to web test parameters dialog box, two requests will be highlighted in the Web Performance Test Editor request tree. The first request will be the request that the extraction rule will be added to. The second request is where the extracted value will be bound.
+     If you choose a dynamic parameter in the **Promote Dynamic Parameters to web test parameters** dialog box, two requests will be highlighted in the Web Performance Test Editor request tree. The first request will be the request that the extraction rule will be added to. The second request is where the extracted value will be bound.
 
 2.  Select or clear the check box next to the dynamic parameters you would like to automatically correlate. By default, all the dynamic parameters are checked.
 

docs/test/generate-and-run-a-coded-web-performance-test.md

@@ -79,10 +79,10 @@ Web performance tests are recorded by browsing through your web app. The tests a
 ## Q&A
 
 ### Q: Can I run more than one test at a time?
- **A:** Yes, use the context menu in Solution Explorer.
+ **A:** Yes, use the context menu in **Solution Explorer**.
 
 ### Q: Should I add a data source before or after I generate a coded test?
- **A:** It is easier to a [data source](../test/add-a-data-source-to-a-web-performance-test.md), before you generate the coded test because the code will be automatically generated for you.
+ **A:** It is easier to add a [data source](../test/add-a-data-source-to-a-web-performance-test.md) before you generate the coded test because the code will be automatically generated for you.
 
  When you run a coded test with a data source, you might see the following error message:
 
@@ -91,4 +91,4 @@ Web performance tests are recorded by browsing through your web app. The tests a
  This can occur because you have a DataSourceAttribute defined for the test class, without a corresponding DataBindingAttribute. To resolve this error, add an appropriate DataBindingAttribute, delete it, or comment it out of the code.
 
 ### Q: Should I add validation and extraction rules before or after I generate a coded test?
- **A:** It is easier to validation rules and extraction rules before you generate the coded test; however, we recommend that you use [coded UI tests](../test/use-ui-automation-to-test-your-code.md) for validation purposes.
+ **A:** It is easier to add validation rules and extraction rules before you generate the coded test; however, we recommend that you use [coded UI tests](../test/use-ui-automation-to-test-your-code.md) for validation purposes.