This topic explains how to use the Microsoft Visual Studio Team System Web test record and playback engine. The following are the basic steps.
Create the scenario before you attempt to automate the test. The scenario outlines the sequence of steps to complete the operation that you are testing.
Record the Web test by following the steps in the scenario, and then save the Web test.
Clean your test environment, and then run the coded test. If your test passes, you can skip step 4.
Create an extraction rule to extract the GUIDs, and then replace the hard-coded GUIDs with the rule. You will receive the exception "There is no context parameter with the name …" when you run the recorded test if a GUID needs to be extracted. There might be more than one GUID that needs to be extracted in a test.
Generate a coded test for the saved test.
Clean your test environment and run the coded test.
You must have the following software installed to follow the procedures in this topic:
Microsoft Visual Studio Team System 2008
Windows SharePoint Services (WSS) 3.0 or Microsoft Office SharePoint Server (MOSS) 2007
The procedures in this topic use a SharePoint team site named TestGuidance, which is located at the URL http://localhost/sites/TestGuidance. However, the procedures will work with any other URL location for the team site.
Use the following steps to create a very simple test method that illustrates the basic concepts involved in creating an automated test for SharePoint.
Creating the scenario involves identifying the pages, data, and clicks that you will enter for the test case. You will follow the scenario script when you use the record and playback engine to create the test. For this scenario example, you browse to http://localhost/sites/TestGuidance and verify that a successful response is returned.
The following procedure describes how to use Visual Studio Team System to record a test.
To record the test
Start Visual Studio, and then create a test project.
On the Test menu, click New Test. The Add New Test dialog box appears.
Select Web Test.
Type http://localhost/sites/TestGuidance as the URL. This starts the record and playback engine, as show in the following illustration.
Record and playback engine
When the browser appears in recording mode, notice that in the Web Test Recorder pane (the left pane) the Record button is selected. Because this scenario is only a single step that retrieves the Web page, click the Stop button (next to the Record button) to stop recording and close Internet Explorer.
On the File menu, click Save to save the Web test.
Note:
In most scenarios, you will see pop-up messages that contain information about detecting dynamic parameters. However, this test does not generate the messages.
After processing is finished, the recorded Web test will appear, showing the steps that were recorded. In this scenario, the test will have a single step for viewing the page.
In this scenario, there is no clean-up required for the test environment. You should be able to run WebTest1.webtest successfully.
The successful test is an indicator that there are no GUIDs to be replaced. Therefore, in this scenario, you do not need to create a GUID extraction rule.
The following procedure describes how to generate the coded test.
To generate the test code
Open WebTest1.webtest, and click Generate Code as shown in the following illustration. (Alternatively, you can right-click WebTest1.webtest, and then click Generate Code.)
Generating the coded test
This produces a C# file named WebTest1Coded, as shown in the following example code.
public class WebTest1Coded : WebTest { public WebTest1Coded() { this.PreAuthenticate = true; } public override IEnumerator<WebTestRequest> GetRequestEnumerator() { // Initialize validation rules that apply to all requests in the WebTest if ((this.Context.ValidationLevel >= Microsoft.VisualStudio.TestTools.WebTesting.ValidationLevel.Low)) { ValidateResponseUrl validationRule1 = new ValidateResponseUrl(); this.ValidateResponse += new EventHandler<ValidationEventArgs>(validationRule1.Validate); } WebTestRequest request1 = new WebTestRequest("http://localhost/sites/TestGuidance/default.aspx"); yield return request1; request1 = null; } }
You can now delete WebTest1.webtest, and use the coded test.
In this scenario, there is no clean-up required for the test environment. You should be able to run the WebTest1Coded test successfully.
When sites and other elements are created in SharePoint, they often have GUIDs associated with them. As a result, a recorded Web test might be tied to the GUIDs created for that site or element, and might not work with a different element instance if you run the test again. Examples of elements that create GUIDs are sites, lists, list items, and Web parts. This topic explains how to write a more complex test method to replace the GUIDs in these cases. Dynamic parameters are used to replace the GUIDs at test execution time.
The following scenario lists the steps that will be recorded.
To create the scenario
Browse to your TestGuidance team site.
Create a subsite under the TestGuidance team site.
Browse to the new subsite.
Create an announcement.
Stop the test.
The following procedure describes how to use Visual Studio Team System to record the test.
To record the test
Start Visual Studio, and then create a test project.
On the Test menu, click New Test. The Add New Test dialog box appears.
Select Web Test.
Name the test WebTest3.
Start the recording, and then perform the scenario steps listed in step 1. Stop recording after you complete the scenario steps. The following illustration shows the test that you created.
Recorded test example
Delete the subsite that was created when you recorded the test, and then run WebTest3 again. The test will fail because the GUID is incorrect, as shown in the next illustration.
Test failure caused by invalid GUID
When you run the test again, it creates another site that has a different GUID. The test attempts to use the GUID created for the original site, which causes the test to fail. To correct the test, you have to locate the GUID, extract it, store it in a dynamic parameter, and then create code to replace the GUID in the generated test with the GUID in the dynamic parameter.
This step outlines how to identify and create a rule to extract GUIDs.
Before you create the extraction rule, click the error and confirm that that the error was caused by an incorrect GUID. In the example there is a 36-digit string—af382975_fa11_4a83_8427_7e7788c3e483—that represents a GUID from the original site created during the test recording session. If you repeat the steps and create another recorded test, you will see a different GUID value for the site that was created during your recording session.
The extraction rule is different for different controls. To extract its value, you must find out what the GUID represents. First, locate the failing request in your scenario.
The request fails because it contains a GUID from the instance of the site used during the recording session. You must update the request to use the dynamic parameter that extracts the GUID from the response for the current instance.
Open the HTML response for the page that you submitted before you received the error (see the next illustration). To identify the GUID, you have to extract a GUID for the next request. This value will be different from the GUID described in the error message.
To extract the value of the GUID
Click the WebTest3 tab.
Select the NewForm.aspx file that appears before the failing step, as shown in the following illustration.
Response and HTML
Click the Response tab.
Most GUIDs start with $m$g in the response. Click View in HTML editor and search for $m$g. Look for the GUID information that follows so that you know what needs to be extracted. There may be more than one GUID, and you will need to determine the correct GUID to use. You can see the build verification test (BVT) cases included with the guidance for examples of more complex cases with multiple GUIDs. In this example, there is only one GUID. You need to extract the following GUID information:
Tag: Input
Attribute: type and its value: button
Attribute with GUID: name
String that contains the GUID
Because the GUID changes each time you run the test, the values that you see will be different from those shown in the following illustration.
GUID information to extract
After you locate the GUID information, you have to add the extract operation to the Web request. Visual Studio Team System has a feature for extracting any value in a Web response. You can use code or a Visual Studio Team System dialog box to add this capability. In this example, you will use the wizard to add the extraction operations. After you complete the wizard, you can generate the C# file, which will form your final SharePoint test method.
To add the extraction rule
Open the WebTest3.webtest file.
Right-click the page request that occurs just before the failing request, and then click Add Extraction Rule. (See the next illustration.)
Adding the extraction rule
The Add Extraction Rule wizard appears (see the next illustration). In the Options box, type the Content Parameter Name. In the Parameters box, type the Tag Name, Attribute Name for the GUID, MatchAttributeName, and Match Attribute Value, based on the information you gathered in the previous procedure.
Add Extraction Rule wizard
Click OK.
You should now see the extract operation attached to the Web test, as shown in the following illustration.
Extract operation added to Web test
The following procedure describes how to generate the coded test from the original recorded Web test and then replace the GUID with the extracted values from the dynamic parameter.
To generate the test code
Open the WebTest3.webtest file, and then click Generate Code as shown in the following illustration. (Alternatively, you can right-click WebTest3, and then click Generate Code.)
Generating the coded Web test
This produces a C# file named WebTest3Coded.
In the C# file, locate the Extract object by searching for the context parameter name. The example used the context parameter name TestValueGUID when the extraction rule was created. See the following illustration.
Locating the extraction object
Create a GUID parameter to capture the extracted dynamic GUID from the extracted context parameter, as shown in the following example.
C#
string TestValueGUID = Context["TestValueGUID"].ToString(); //Now extract the GUID the string int i = TestValueGUID.IndexOf('_') + 1; //Note the underscore, not dash TestValueGUID = TestValueGUID.Substring(i, 36);
The test framework runtime extracts the complete GUID string from the response and puts it into the context. The following illustration shows the code example above inserted in the test code to save the extracted GUID in the variable TestValueGUID.
GUID parameter inserted in the test code
Locate the hard-coded GUID value in the C# code for the failing request.
Find the GUID value that needs to be replaced by the dynamic parameter value from the code you created in step 3. To do this, look at the error information for the failed request. In the example, the GUID is the 36-digit string af382975_fa11_4a83_8427_7e7788c3e483.
Locate the numeric strings in the C# code, as shown in the following illustration.
Numeric strings in C# code
Replace the GUID value af382975_fa11_4a83_8427_7e7788c3e483 with the GUID parameter string“+TestValueGuid.Replace(“-“,”_”).ToString()+” as shown in the following illustration.
Replacing the GUID value
Save the files and then build the solution. Make sure that it compiles successfully.
This section describes how to clean your test environment before you run the coded test.
To clean the environment
Delete all generated subsites under your test team site.
Open the Test List View, and then select the C# test method that you just created.
Run the test. It should be successful.
If the test fails, check the following:
Have you edited and extracted the GUID correctly?
Have you missed a GUID value?
If the test still fails, repeat the steps to replace the GUID value dynamically.